SuperCatch

Inspect an exact price plan

supercatch_get_price_plan

Read-onlyIdempotent

Read an owned connection-bound price plan, its expiry and trusted approval state without changing it. Use for an exact, frozen seller price workflow under this connection's separate price-write consent. No inventory, order, automation settings or listing publication changes. Local completion does not establish marketplace prices. Returns a strict baseline plan, durable operation or history envelope with explicit local outcomes. Stored approval tokens and worker lease IDs are never returned. Requires OAuth store:prices:write consent. Requires store:prices:write and current EDIT_LISTINGS permission on an approved owned store. Plans expire in nine minutes and contain up to 125 exact listing IDs. Each execution call processes at most five remaining targets. Reuse the original plan/key until terminal; released leases can continue immediately and abandoned leases wait two minutes. Status reads do not resume work. Plan and item reads are paginated. Read-only; no execution or approval. Foreign, revoked or expired grants and stale versions fail. Unapproved plans require web review. Idempotency-key reuse for another plan conflicts; a lost response is recovered through supercatch_list_operations or supercatch_get_operation before any new action.

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": {
      "plan_id": "price-plan-id"
    },
    "name": "supercatch_get_price_plan"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum frozen items returned on this page. Execution batch size is independent of read pagination.
`cursor`	No	Opaque next_cursor from this exact plan or operation with the same page size.
`plan_id`	Yes	Owned connection-bound plan ID returned by supercatch_prepare_price_changes.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses OAuth consent and EDIT_LISTINGS permission requirements, nine-minute expiry, up to 125 listing IDs, five-target execution batches, lease timing, pagination, failure conditions and web review for unapproved plans. It also states that approval tokens and worker lease IDs are never returned.

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 front-loads the read-only purpose, then adds usage, auth, limits and recovery guidance in a dense but mostly purposeful sequence. It has some redundancy around read-only/no execution and repeated auth requirements, and packs many operational rules into one paragraph.

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?

Given the tool's complexity, the description covers permissions, expiry, pagination, lease behavior, failure modes, recovery paths and the distinction between local completion and marketplace prices. Because an output schema exists, it does not need to explain the return envelope in detail.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so plan_id, limit and cursor are already documented in the schema. The description adds lifecycle meaning for plan_id—it comes from prepare_price_changes, expires in nine minutes, and should be reused until terminal—and notes that plan and item reads are paginated.

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: read an owned connection-bound price plan, its expiry and approval state without changing it. It clearly distinguishes inspection from execution/approval and from inventory, order, automation or publication changes.

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

Usage Guidelines5/5

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

It says to use this for the exact frozen seller price workflow and explicitly rules out execution, approval, inventory, order, automation settings and listing publication changes. It also names recovery alternatives, supercatch_list_operations and supercatch_get_operation, for a lost response.

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?