Retrieve a specific payment method event by token. This read-only tool provides event details for inspecting payment activity.
Retrieves a specific payment method event by token. This tool ONLY reads data.
| Name | Required | Description | Default |
|---|---|---|---|
| event_token | Yes | The token of the event |
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 merely restates 'ONLY reads data' without disclosing additional behavioral traits like response format or permissions.
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 concise sentences, front-loaded with purpose, no wasted 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?
Adequate for a simple read operation with one parameter and no output schema, but lacks details on return values or error conditions.
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 'The token of the event' already in schema. The description adds no extra meaning for the parameter.
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?
Clearly states it retrieves a specific payment method event by token, distinguishing it from siblings like spreedly_event_show (generic event) and spreedly_payment_method_list_events (list).
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?
Implies read-only usage with 'ONLY reads data,' but provides no explicit guidance on when to use vs. alternatives (e.g., spreedly_event_show).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.