Fetch paginated event summaries from Spreedly to monitor transaction and gateway activity.
Lists events in your Spreedly environment with pagination. Returns event summaries. This tool ONLY reads data.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of events to return | |
| order | No | Sort order | |
| event_type | No | Event types to return | |
| since_token | No | Pagination token to fetch events after |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already set readOnlyHint=true and openWorldHint=false. The description adds 'This tool ONLY reads data,' which reinforces the annotation but does not provide additional behavioral traits (e.g., authentication needs, rate limits, or side effects). The mention of pagination is useful context beyond the schema.
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 extremely concise: three short sentences that front-load the core action and key feature (pagination). No verbose or redundant phrasing. Every sentence adds value.
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 has 4 parameters and no output schema. The description covers the primary purpose and mentions pagination, but does not detail the output structure beyond 'event summaries.' Given the lack of required parameters and simple list operation, it is mostly adequate. Missing details about the output format, but acceptable for a list tool.
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 description coverage is 100%, so the input schema already documents each parameter. The tool description adds no extra meaning beyond mentioning pagination generically. Per rules, baseline is 3 when coverage is high.
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 action ('Lists events'), the resource ('in your Spreedly environment'), and includes key features like pagination. The phrase 'Returns event summaries' further clarifies the output. It distinguishes from sibling tools by explicitly noting it's a list operation, while siblings like spreedly_event_show are show 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?
The description lacks guidance on when to use this tool versus alternatives such as spreedly_event_show or spreedly_protection_list_events. There is no mention of prerequisites, when not to use it, or specific contexts. The read-only hint is implicit but not framed as a usage guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.