get_my_permissionsRetrieve the permissions assigned to the authenticated user based on their roles. Use this to verify access rights and troubleshoot authorization issues.
Lista los permisos del usuario autenticado según sus roles.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description gives minimal behavioral details. It states the action (lists permissions) and the source (roles), but does not mention side effects, authentication requirements, return format, or error scenarios. Since no annotations are present, the description carries the full burden and falls short.
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 extremely concise and well-structured. One sentence conveys the essential information without any superfluous content. The verb is front-loaded, making the purpose immediately clear.
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?
For a simple read operation with no parameters and no output schema, the description is adequate. It specifies the output (permissions) and the determining factor (roles). Some details like pagination or response format are omitted, but they are not critical for such a straightforward tool.
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 tool has no parameters, and the schema correctly reflects this with an empty properties object. Since there are no parameters to describe, the baseline of 4 is appropriate. No additional parameter explanation is needed.
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's purpose: listing the permissions of the authenticated user based on their roles. It uses a specific verb ('Lista') and a well-defined resource ('permisos del usuario autenticado'), which distinguishes it from general permission tools like list_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 provided on when to use this tool versus alternatives such as list_permissions or get_my_scopes. The description implies it is for the current user's permissions, but it does not state when this tool should be preferred over others.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.