Skip to main content
Glama
Sign In

SuperCatch

by com.supercatch
OverviewDiscussionsAdmin

Prepare one first shipment

supercatch_prepare_order_shipment

Prepare an exact first-shipment review for one untracked eligible website order. Ship one owned pending, paid or processing website order with native verified tracking. Review the exact status transition and private notifications in SuperCatch. Tracking corrections, marketplace orders, label purchases, payment, refund, stock changes, arbitrary messages, bulk targets or active order.updated webhook destinations. An expiring plan or durable local shipment receipt with separate email and in-app outcomes. Local shipment, email acceptance and carrier delivery are distinct. Private notification recipients and content remain in native review. Requires OAuth store:orders:shipment:write consent. Requires separate store:orders:shipment:write consent, current MANAGE_ORDERS permission and an approved owned store. Tracking-correction and read grants do not authorize a first shipment. Conversational approval does not replace exact native review. Saves a private review plan and obtains native tracking verification. It does not mark the order shipped or dispatch buyer notifications. Foreign, stale, already shipped, unapproved or expired plans and revoked grants fail closed. Recover the same plan and original key after uncertainty. Unknown email outcomes cannot be resent; in-app recovery uses the same stable event identity.

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": {
      "carrier": "UPS",
      "order_id": "owned-unshipped-order-id",
      "tracking_number": "1Z999AA10123456784",
      "expected_version": "2026-11-06T12:00:00Z"
    },
    "name": "supercatch_prepare_order_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrierYesCarrier for this first shipment.
order_idYesOne exact owned website order awaiting its first shipment.
tracking_numberYesTracking identity verified by the native carrier owner.
expected_versionYesExact current order version; changes require a new review.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real value beyond the annotations: it discloses the required scopes ('store:orders:shipment:write'), the MANAGE_ORDERS permission and approved-store prerequisite, states 'It does not mark the order shipped or dispatch buyer notifications,' and enumerates fail-closed conditions (foreign, stale, already shipped, unapproved, expired plans, revoked grants). However, the required-scope sentence is stated twice in near-duplicate form, and the recovery/idempotency story ('Recover the same plan and original key after uncertainty,' 'in-app recovery uses the same stable event identity') is in tension with idempotentHint=false without being reconciled for the agent.

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

Conciseness2/5

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

The content is dense and front-loaded reasonably well, but it is delivered as a string of telegraphic sentence fragments and noun lists that are hard to parse and contain repetition (the consent requirement appears twice). Several clauses, such as 'An expiring plan or durable local shipment receipt with separate email and in-app outcomes,' are grammatically incomplete and force the reader to reconstruct the intended relationship.

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

Completeness4/5

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

For a mutating, permission-gated tool with an output schema, the description covers the essentials: prerequisites, scope requirements, failure modes, recovery-after-uncertainty guidance, and the crucial assurance that no shipment or buyer notification is dispatched. Return values need not be explained because an output schema exists. Minor gaps remain around what exactly the saved review plan contains, but the coverage is strong overall.

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 four parameters are already documented, and the description mostly reinforces them at a conceptual level ('exact' order, 'native verified tracking,' version changes requiring a new review). It does not add format or syntax detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The opening sentence names a specific verb and resource with scope: 'Prepare an exact first-shipment review for one untracked eligible website order,' and the follow-up restricts it to 'owned pending, paid or processing website order with native verified tracking.' It implicitly separates itself from supercatch_prepare_order_tracking and execute_order_shipment by excluding 'Tracking corrections' and stating it 'does not mark the order shipped,' but it never names the sibling tools an agent should use instead, so the differentiation is inferred rather than stated.

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?

Usage conditions are unusually explicit: eligibility ('untracked eligible website order,' 'pending, paid or processing'), plus a long exclusion list covering tracking corrections, marketplace orders, label purchases, payment, refund, stock changes, bulk targets and active webhook destinations. What keeps it from a 5 is that exclusions are given as a bare noun list with no routing – the agent is told what this tool is not for but not which sibling handles each case.

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