SuperCatch

Inspect my recorded collection

supercatch_list_collection_items

Read-onlyIdempotent

Traverse recorded catalog-backed collection items in the authenticated account. Reference-only ownership is excluded. Recorded quantities and acquisition dates do not verify physical possession or purchase provenance. Titles, costs, notes, certificates, photos, valuations, transfers and automation data are omitted; this is not stock or purchase-history verification. Use supercatch_list_collection_items 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 account:read consent. Returns only the current verified connection; discovery cannot grant access. 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": {
      "limit": 10
    },
    "name": "supercatch_list_collection_items"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum recorded collection items on this live page; keep this limit with its cursor.
`cursor`	No	Opaque next_cursor bound to this account, connection, environment, collection and page size.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, but the description adds substantial context beyond them: OAuth account:read consent is required, discovery cannot grant access, the call is unmetered, expired cursors require a fresh search, and failures (invalid fields, unavailable stores, foreign/deleted targets) are explicit and leak no private records. That is genuinely useful operational detail an agent would not get from the annotation block alone.

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 purpose is front-loaded, but the body is bloated with boilerplate and self-reference: 'Use supercatch_list_collection_items for this read' adds nothing, and the repeated negative scoping ('not stock or purchase-history verification,' 'no prices, inventory, orders, automation...') could be compressed into one clause. Several sentences restate the read-only guarantee already carried by annotations.

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?

With an output schema present and 100% parameter coverage, the description need not explain return values, and it correctly focuses on auth requirements, error behavior, pagination expiry, and field omissions. The only real gap is the absence of sibling routing guidance, which is a usage concern rather than a completeness one.

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 limit and cursor are already fully documented, making 3 the baseline. The description does add one piece of meaning beyond the schema — 'Expired cursors require a fresh search' — which explains cursor lifecycle, but it does not otherwise elaborate on limit/cursor interaction.

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?

States a specific verb and resource: 'Traverse recorded catalog-backed collection items in the authenticated account,' plus a scope exclusion ('Reference-only ownership is excluded'). This distinguishes it from a single-item read like supercatch_get_collection_item, but no sibling is named explicitly, 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 Guidelines2/5

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

The only usage sentence is 'Use supercatch_list_collection_items for this read in the connected account,' which restates the tool name rather than explaining when to pick it over supercatch_get_collection_item, supercatch_list_watchlist_items, or other list tools. There are negative scope hints ('this is not stock or purchase-history verification') but no positive routing guidance or prerequisites for choosing this tool.

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?