Metadata service - service name duplication across stacks is a problem

If I have two stacks with identical service names within them - eg stack-a/svc-z and stack-b/svc-z - I can use metadata services to discover that each stack has a service named z in it by calling .../stacks/<name>/services, but I cant use stack name as a prefix when calling …/services/ - eg ../services/stack-a%2Fsvc-z. (URLEncode the stack/svc parameter)

Is there another way to do this?

We know this is a problem and will be addressing it with a new revision of the metadata API in an upcoming release.