list_oauth_client_scopesLists OAuth scopes available for assignment to OAuth clients within a specified tenant, using the tenant ID to retrieve the scopes.
Lista los scopes OAuth disponibles para asignar a clientes del tenant.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID del tenant |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No behavioral information is disclosed beyond the basic listing action. The description does not mention whether the operation is read-only, requires specific permissions, or returns a particular format. Since no annotations are present, the description carries full responsibility for transparency but fails to provide details.
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 with no redundant words. It effectively communicates the core functionality without unnecessary elaboration.
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 listing operation, the description provides the essential purpose and parameter. However, it lacks guidance on usage context, expected output, or edge cases, making it only partially complete for an agent that needs to decide when and how to invoke it.
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 input schema provides a description for the single parameter 'id' ('ID del tenant'), so the meaning is clear. The tool description does not add any additional context or clarification about this parameter, but the schema already covers it adequately.
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: to list OAuth scopes assignable to clients of the tenant. It uses a specific verb ('list') and identifies the resource ('OAuth scopes') and context ('for clients of the tenant'), distinguishing it from the sibling tool 'list_oauth_scopes' which likely lists all scopes.
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 does not explicitly indicate when to use this tool versus alternatives such as 'list_oauth_scopes' or 'list_available_tenants'. No context or conditions for selection are provided, leaving the agent to infer use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.