create_roleCreate a role inside a specific scope or tenant to manage access permissions.
Crea un rol dentro de un scope/tenant.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Nombre del rol | |
| extra | No | ||
| idScope | Yes | ID del scope (tenant) | |
| description | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only says 'creates a role' without disclosing side effects, permissions required, failure modes, or return behavior. This leaves the agent uncertain about what happens on success or error.
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, direct sentence with no unnecessary words or redundancy. It is concise and well-structured for a simple create operation.
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?
The description gives only the fundamental purpose. It omits critical context such as parameter details, required fields beyond what the schema shows, return values, or potential constraints (e.g., duplicate names). This incompleteness could lead to incorrect invocation.
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 has 4 parameters but only 2 are described (idScope and name). The tool description does not add any parameter explanations, so the 'description' and 'extra' parameters remain ambiguous. With only 50% schema coverage, the description fails to compensate for the lack of clarity.
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 creates a role within a scope/tenant, using the specific verb 'Crea' and resource 'rol'. It distinguishes itself from sibling tools like update_role and delete_role, making its purpose unambiguous.
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?
The description provides clear context that this is for creating a role, and the tool name and sibling set make it evident when to use it over update_role or delete_role. However, it does not explicitly mention alternatives or conditions for use, though the context is strong enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.