list_oauth_clientsLists OAuth clients for a specified tenant. Provide the tenant ID to retrieve all associated OAuth client configurations.
Lista los clientes OAuth del tenant indicado.
| 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 annotations and no mention of side effects, return shape, or read-only guarantees; verb 'Lista' suggests read-only but behavior is not fully disclosed.
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?
Single concise sentence, directly states purpose without extra words.
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 list operation with one well-described parameter and no output schema, the description is adequate, though it lacks any usage context or alternatives.
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 sole parameter is already described in the schema as 'ID del tenant'; description adds no extra semantic clarification but schema coverage is complete.
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?
Description uses specific verb 'Lista' and resource 'clientes OAuth', scoped by tenant, clearly distinguishing from create/update/delete and other list tools.
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 on when to prefer this tool over siblings like list_oauth_client_scopes; usage is implied by name/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.