Retrieve merchant profile details by token to view configuration, gateway settings, and related data.
Retrieves details of a single merchant profile. This tool ONLY reads data.
| Name | Required | Description | Default |
|---|---|---|---|
| merchant_profile_token | Yes | The token of the merchant profile |
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. Description adds 'This tool ONLY reads data', reinforcing but not adding new behavioral context beyond what annotations provide.
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?
Two sentences, no wasted words. Critical information is front-loaded: action and resource in first sentence.
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 retrieval tool with one parameter and no output schema, the description and annotations together fully specify the tool's purpose and safety.
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?
Schema coverage is 100% with description for each parameter. The description does not add extra meaning beyond what schema already states for 'merchant_profile_token'.
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 explicitly states 'Retrieves details of a single merchant profile', using specific verb 'Retrieves' and resource 'merchant profile'. It clearly distinguishes from sibling tool 'spreedly_merchant_profile_list' which lists all profiles.
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 use this tool vs alternatives. The description implies it's for a single token, but doesn't mention when not to use or suggest alternatives like list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.