Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tcgplayer_price_guide

Read-only

Get TCGplayer's price guide for a whole set by set_id and return one row per card, condition and printing: card id, name, collector number, rarity, condition, printing, language, low price, market price and units sold, up to 500 rows per page. Use this to price an entire set in a few calls; get set_id from tcgplayer_sets and card ids for tcgplayer_product from the rows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "set_id": "<set_id>"
    },
    "name": "tcgplayer_price_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 500; defaults to 100
offsetNoRows to skip; use the previous response's next_offset
set_idYesNumeric set id from tcgplayer-sets (the id field)

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so safety is covered. The description adds real value beyond them by disclosing the result shape (one row per card/condition/printing), the exact fields returned, and the pagination ceiling of 500 rows per page. It could still note rate limits or ordering, which keeps it at 4.

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

Conciseness5/5

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

Two sentences, zero filler. Scope and row grain come first, then the workflow hint, with the pagination limit embedded inline rather than as a separate sentence.

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?

An output schema exists, so return details are technically optional, but the description's field list and pagination note make the tool self-sufficient for a bulk-pricing workflow. Combined with readOnly/openWorld annotations and full schema coverage, an agent has what it needs to call it correctly.

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 coverage is 100%, so baseline is 3. The description goes beyond it by explaining where set_id originates (tcgplayer_sets) and that limit/offset cap at 500 rows per page, giving practical meaning to the pagination parameters. It doesn't restate offset semantics itself, leaving that to the schema.

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 ("Get TCGplayer's price guide") and pins down the grain: one row per card, condition and printing for a whole set, which separates it from per-product siblings like tcgplayer_product and tcgplayer_price_history. It names tcgplayer_sets and tcgplayer_product but as input sources, not for differentiation, so it stops just short of full sibling disambiguation.

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?

"Use this to price an entire set in a few calls" gives a concrete use case that implies the bulk-PvP scenario versus single-card lookups. It also routes the agent to tcgplayer_sets for the id and back to tcgplayer_product from the returned rows. No explicit when-not-to-use or named alternative for single-card pricing, so not a 5.

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

All Crawlora MCP 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