Skip to main content
Glama
Sign In

SuperCatch

by com.supercatch
OverviewDiscussionsAdmin

Inspect one image from my store listing

supercatch_get_listing_image
Read-onlyIdempotent

Return one owned listing photograph as actual MCP image content for visual inspection. Use when identifying visible card details, checking a pictured label or comparing front/back views. Obtain listingId and image order from supercatch_list_store_listings; imageIndex defaults to zero. Use supercatch_list_store_listings for image URLs without loading pixels. Use supercatch_get_product for public offer facts. Photographs alone do not certify grade or authenticity, and this tool cannot inspect arbitrary URLs or another seller's private listing. Returns one metadata-stripped JPEG image block plus listing ID, source URL, image count/index and actual dimensions. maxEdge defaults to 1024; 768 and 1536 are supported. Images preserve aspect ratio without cropping or enlargement. Requires OAuth store:read consent. The connected account must own an approved store. Read-only; downloads and resizes the selected image without changing listings, source files, prices or inventory. Unowned/deleted listings, missing indexes and unsafe/unsupported images return no image. Download, decoding and size failures remain errors; request maxEdge 768 if the encoded image exceeds the budget. Missing details must not be inferred.

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": {
      "listingId": "owned-listing-id"
    },
    "name": "supercatch_get_listing_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxEdgeNoMaximum width or height in pixels. Preserves the entire image and aspect ratio, without enlargement. Request 768 if the encoded image exceeds the response budget.
listingIdYesOwned listing ID returned by supercatch_list_store_listings; not a catalog ID or URL.
imageIndexNoZero-based position in that listing's imageUrls. Omit for the first image; request another index for another view.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description adds useful behavioral context: OAuth store:read consent, approved-store ownership, metadata-stripped JPEG output, aspect-ratio preservation, failure semantics, and response-budget guidance. It does not contradict the annotations.

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 is front-loaded with purpose and usage, and most sentences carry useful guidance. It is somewhat long and repeats schema details such as the default maxEdge and supported enum values, so it is not maximally concise.

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 tool with no output schema and three parameters, the description is complete: it explains the return content, authentication and ownership requirements, supported resizing behavior, and what happens on failures. An agent has enough context to invoke it correctly.

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 schema already documents listingId, imageIndex, and maxEdge thoroughly. The description mostly restates those meanings, including defaults and the source of IDs, rather than adding substantial new parameter semantics.

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: returning one owned listing photograph as actual MCP image content for visual inspection. It clearly distinguishes this from sibling tools such as supercatch_list_store_listings and supercatch_get_product, so an agent can tell what this tool is for without opening the schema.

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 gives explicit when-to-use examples, including identifying visible card details and comparing front/back views. It also names alternatives for getting URLs without loading pixels and for public offer facts, and it excludes arbitrary URLs and another seller's private listing.

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