Sinatra Routes ambiguous

[granolocks]

Compare the following:

# request of Snapi root path
curl localhost:4567/
{"status":200,"data":{"ninja":{"sneak":{"return_type":null,"arguments":[]},"attack":{"return_type":null,"arguments":[{"name":"foe","required":true,"type":"stri
ng"}]},"defend":{"return_type":null,"arguments":[{"name":"weapon","required":true,"type":"string"}]}}},"execution_time":2.833e-05}

# request of Snapi base path for ninja capability
curl localhost:4567/ninja
{"status":200,"data":{"sneak":{"return_type":null,"arguments":[]},"attack":{"return_type":null,"arguments":[{"name":"foe","required":true,"type":"string"}]},"defend":{"return_type":null,"arguments":[{"name":"weapon","required":true,"type":"string"}]}},"execution_time":4.5747e-05}

These outputs need to self identify whether or not they are a capability or a function declaration. This needs to be fixed for functionality disclosure to be more meaninful..