SuperCatch

Inspect postage estimates for my order

supercatch_get_order_label_rates

Read-onlyIdempotent

Read current native postage estimates for an exact owned order and its current parcel. Returns USD carrier postage, service fee, reserve and seller share separately; null prices remain unknown during provider outages. No label is purchased or reserved. Rates have no guaranteed expiry and require fresh financial review before purchase. Inspect the order with supercatch_list_store_orders first. Use supercatch_get_order_label_rates for this read in the connected account. Supply only the fields in its strict input schema. No prices, inventory, orders, automation, marketplace publication or provider configuration are changed. Returns a Shared MCP Baseline 1.0.0 envelope with explicit scope, provenance, unknown values, omissions and typed errors. Requires OAuth store:read consent. Requires store:read consent, a currently approved owned store and live MANAGE_ORDERS permission. Buyer addresses, contact details, payment references and raw provider data are withheld. Quotes do not authorize label purchase. Read-only and unmetered; no persistent plans or provider submissions. Invalid fields, unavailable stores and foreign or deleted targets fail without private records. Expired cursors require a fresh search. Provider failures are explicit errors.

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": {
      "order_id": "owned-order-id"
    },
    "name": "supercatch_get_order_label_rates"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes	Exact order ID returned by supercatch_list_store_orders for the connected store.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / order_id / description

Previous value: -"Exact order ID returned by list_store_orders for the connected store."New value: +"Exact order ID returned by supercatch_list_store_orders for the connected store."

AddedNov 5, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses null prices during provider outages, no guaranteed rate expiry, required OAuth store:read consent plus live MANAGE_ORDERS permission, withheld buyer/payment data, unmetered behavior, and explicit error semantics. This is unusually rich behavioral context that an agent could not infer from annotations alone.

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

Conciseness3/5

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

The key scope and safety facts are front-loaded, but the text is bloated with redundancy: consent is stated twice ('Requires OAuth store:read consent. Requires store:read consent...') and 'Use supercatch_get_order_label_rates for this read in the connected account' restates the tool name without adding information.

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 single-parameter read tool with an output schema, the description covers scope, auth requirements, data withholding, error behavior, and the no-purchase guarantee. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the single order_id parameter is fully documented in the schema, so the description only says to 'supply only the fields in its strict input schema.' It adds no format or sourcing detail beyond what the schema already provides, matching the baseline 3.

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 opens with a specific verb and resource: 'Read current native postage estimates for an exact owned order and its current parcel.' It also enumerates what is returned (carrier postage, service fee, reserve, seller share), which distinguishes it from siblings like supercatch_get_order or supercatch_list_store_orders.

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 an explicit prerequisite ('Inspect the order with supercatch_list_store_orders first') and clarifies that no label is purchased or reserved, which steers agents away from purchase flows. It lacks an explicit when-not statement or a named alternative for related quote needs, so it falls short of a 5.

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

All SuperCatch tools Inspect

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

Need Help?