Skip to main content
Glama
Sign In

SuperCatch

by com.supercatch
OverviewDiscussionsAdmin

My store's orders

supercatch_list_store_orders
Read-onlyIdempotent

List orders placed with the connected seller's store, newest first. Use for seller fulfillment oversight; status filters sales orders and nextCursor continues with the same filters and limit. The buyer's personal purchases, shipping updates and refunds are outside this read. Returns store order numbers, status, totals, tracking and dates, plus pagination and generation time. Requires OAuth store:read consent. The connected account must own an approved store. Read-only; no order, payment or tracking changes. An account without an approved store receives a tool error. No matches return an empty page; malformed continuation cursors return a tool error.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3
    },
    "name": "supercatch_list_store_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows per page (1-50); defaults to 20.
cursorNoContinue with nextCursor from the previous page, keeping the same status and limit.
statusNoOnly return orders in this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond read-only annotations, the description discloses OAuth scope requirements, the approved-store prerequisite, the tool error for accounts without an approved store, empty-page behavior, and malformed-cursor errors. It also notes that there are no order, payment, or tracking changes, reinforcing the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and scope before covering returns, auth, prerequisites, and errors. It is somewhat long and includes minor redundancy, such as stating the approved-store requirement in two separate ways, but the length is justified by the operational details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only paginated listing tool with auth and prerequisite constraints, the description covers purpose, exclusions, pagination continuity, return fields, and key failure modes. No output schema exists, and the description provides enough information about what is returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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 explains limit, cursor, and status. The description adds a little context, such as status filtering sales orders and cursor continuity, but mostly restates what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: list orders for the connected seller's store, newest first. It also distinguishes seller fulfillment orders from the buyer's personal purchases, shipping updates, and refunds, making the scope clear without needing another tool's schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear use case, seller fulfillment oversight, and explicitly excludes buyer personal purchases, shipping updates, and refunds. It does not name specific sibling alternatives such as list_account_orders or get_order, so there is room for more explicit routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SuperCatch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources