Retrieve paginated transaction summaries from Spreedly, filtering by state, count, and sort order to monitor payment activity.
Lists transactions in your Spreedly environment. Returns transaction summaries with pagination. This tool ONLY reads data.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of transactions to return | |
| order | No | Sort order | |
| state | No | Filter transactions by state | |
| since_token | No | Pagination token |
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, so the description's 'ONLY reads data' is redundant but consistent. It adds that results are transaction summaries with pagination, which is useful beyond annotations.
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. Front-loaded with the primary action and key features (summaries, pagination, read-only).
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?
Given no output schema, the description mentions summaries and pagination, but could specify what fields are in a summary. Still sufficient for a simple 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%, with each parameter already described. The description adds no further parameter details, so baseline 3 is appropriate.
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 tool lists transactions and returns summaries with pagination. It distinguishes itself from siblings like spreedly_transaction_show (single transaction) and spreedly_gateway_list_transactions (by gateway).
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 says it lists transactions and is read-only, but does not specify when to prefer this over alternatives like spreedly_gateway_list_transactions or spreedly_transaction_show. Usage context is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.