store_ordersList orders placed with the signed-in seller's SuperCatch store, newest first: order number, status, totals, tracking, and dates. Requires connecting a SuperCatch account that owns an approved store.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum rows to return (1-50). | |
| cursor | No | Continue with nextCursor from the previous page, keeping the same status and limit. | |
| status | No | Only return orders in this status. |
Changes observed during successful MCP inspections.
Input schema / properties / cursorAdded value: +{
+ "description": "Continue with nextCursor from the previous page, keeping the same status and limit.",
+ "maxLength": 512,
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful context the annotations don't carry: results are newest-first and access requires an approved store on a connected account.
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, zero padding: what is returned and the sort order come first, the access prerequisite second. No redundancy with the title or annotations.
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?
There is no output schema, and the description partly compensates by naming the fields returned (order number, status, totals, tracking, dates). Combined with the fully documented schema this is largely complete, though a note on result volume/paging expectations would close the last gap.
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 limit, cursor and status are already fully documented in the schema. The description adds no syntax or filtering detail beyond implying a newest-first ordering relevant to cursor paging, so baseline 3 applies.
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?
States a specific verb and resource ("List orders") scoped to the signed-in seller's SuperCatch store, and enumerates the returned fields plus sort order. It doesn't explicitly distinguish itself from the sibling my_orders (buyer-side orders) or lookup_store, leaving that distinction to inference.
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?
Adds a real prerequisite: a connected SuperCatch account that owns an approved store. However, it never says when to use this versus my_orders or lookup_store, and gives no guidance on filtering strategy despite exposing a status enum.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.