The only supported way to get that information is to use Moose's meta model, which will also work against Moo classes. Poking into Moo's internals is unsupported and could break at any time.

A better question is why you are looking for this information in the first place. It seems like a case where you are trying to answer the wrong question.