Retrieve details of a specific SCA provider using its token. This read-only operation returns provider information for payment management.
Retrieves details of an SCA provider. This tool ONLY reads data.
| Name | Required | Description | Default |
|---|---|---|---|
| sca_provider_token | Yes | The token of the SCA provider |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. The description adds 'This tool ONLY reads data', which is consistent but does not provide extra behavioral context like rate limits or side effects beyond what annotations convey.
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 consists of two concise sentences, each delivering essential information. No wasted words; the read-only emphasis is front-loaded.
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 tool is simple with one parameter and no output schema. The explanation covers purpose and read-only nature, which is sufficient for a straightforward retrieval. However, lacking any hint about the response format or fields returned limits completeness slightly.
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 single parameter 'sca_provider_token' is described in the schema as 'The token of the SCA provider', and schema coverage is 100%. The description adds no additional semantic value beyond the schema.
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 'Retrieves details of an SCA provider', specifying the verb (retrieves) and resource (SCA provider details). Among sibling tools, it distinguishes itself from general gateways or payment methods by specifying 'SCA provider'.
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 gives no explicit guidance on when to use this tool versus alternatives, such as similar show tools for other entities (e.g., spreedly_gateway_show, spreedly_protection_show_provider). It only implies read-only usage but lacks differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.