Skip to main content
Glama
Sign In

SuperCatch

by com.supercatch
OverviewDiscussionsAdmin

My SuperCatch watchlist

supercatch_list_account_watchlist
Read-onlyIdempotent

List the connected account's saved watched listings. Use to review saved cards and price-alert targets; nextCursor continues the watchlist with the same limit. General marketplace discovery and adding/removing watches or alerts are outside this read. Returns watched items with title, price, condition, listing status, alert target and product URL, plus total and pagination. Requires OAuth account:read consent. Read-only; no watchlist or notification settings change. 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_account_watchlist"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, but the description adds real behavioral context beyond them: the required OAuth scope (account:read), the exact returned fields plus total and pagination, empty-page behavior on no matches, and a tool error on malformed cursors. That covers the operational edge cases an agent needs before calling.

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?

Front-loaded with purpose, then usage boundary, then return shape and auth, then error behavior — a sensible ordering with no filler. It is dense to the point of being list-like, but nearly every clause carries a distinct fact.

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?

With no output schema, the description compensates by enumerating the returned fields and totals/pagination, and it supplies the auth requirement and failure modes. For a two-parameter read tool, nothing needed to call it correctly appears to be 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%, so both parameters are already documented in the schema. The description only reinforces that nextCursor continues paging with the same limit, which is essentially a restatement of the cursor parameter's own description rather than added semantics.

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: 'List the connected account's saved watched listings', with scope narrowed to the connected account rather than the whole marketplace. The gap is sibling differentiation: a near-identical sibling, supercatch_list_watchlist_items, is never mentioned, so an agent must infer which watchlist tool to pick.

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?

Gives a positive use case ('review saved cards and price-alert targets') and explicit exclusions ('general marketplace discovery and adding/removing watches or alerts are outside this read'). It stops short of naming the alternative tools an agent should use for those excluded cases, so selection still requires cross-referencing sibling names.

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