list_permissionsLists permissions for a tenant, returning a flat permission tree. Provide a tenant ID to scope results.
Lista los permisos (árbol aplanado) del tenant del token.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ID de scope (se usa como tenant de referencia) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The verb 'Lista' implies a read-only operation and 'árbol aplanado' hints at the return shape, but no explicit statement about side effects, required permissions, or error behavior is included. With no annotations, the description carries the burden and only partially covers it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that immediately conveys the tool's purpose and scope, with no superfluous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool signature and single optional parameter, the description provides enough context for selection and invocation. It could mention the output structure more explicitly, but 'árbol aplanado' gives a reasonable indication.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes the optional 'id' parameter as 'ID de scope (se usa como tenant de referencia)', so the tool description adds no further meaning. Schema coverage is 100%, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists permissions for the token's tenant as a flattened tree, which is a specific verb and resource and distinguishes it from related tools like list_role_permissions or get_my_permissions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given about when to use this tool versus alternatives such as list_role_permissions or get_my_permissions. The context is implied by the description but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.