Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

pricecharting_product

Read-only

Get one PriceCharting product's prices and recent sales: current prices by condition or grade with their latest change, the full price guide (ungraded through BGS 10 for cards), attributes such as publisher, release date and card number, and recent completed eBay and TCGplayer sales per grade. Pass the product id, its pricecharting.com address, or console and slug. Use after pricecharting_search or pricecharting_console.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pricecharting_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPriceCharting product id from search or console results; costs one extra request to resolve
urlNoA pricecharting.com product page address, instead of id or console and slug
slugNoProduct slug from pricecharting.com/game/<console>/<slug>; use with console
consoleNoConsole or set slug (for example pokemon-base-set); use with slug

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds that the payload spans multiple data families (current prices, guide, attributes, sales) so the agent knows to expect a large composite read. It does not mention rate limits, per-source latency, or what happens for a product without recent sales.

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?

Purpose is front-loaded in the first clause and the identifier options and workflow hint follow in a short closing sentence. The middle enumeration is dense and slightly list-like, but each item maps to a distinct returned data family rather than padding.

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?

An output schema exists, all four parameters are fully described, and annotations cover read safety — so the description only needs to cover scope and invocation. It does both, including how to address the product and where the identifiers come from.

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, but the description adds genuinely useful framing beyond per-field text: three interchangeable addressing modes (id, pricecharting.com URL, or console + slug pair) are stated together. It does not repeat the schema's note that resolving an id costs an extra request.

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?

States a specific verb and resource ('Get one PriceCharting product's prices and recent sales') and then enumerates exactly what is returned: per-condition/grade prices with latest change, full price guide, attributes, and recent eBay/TCGplayer sales. That detail distinguishes it from pricecharting_search and pricecharting_console, which it names.

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 after pricecharting_search or pricecharting_console' gives a clear workflow entry point and implicitly frames this as the detail step following discovery. It does not say when to prefer the sibling pricecharting_price_history instead of this tool for historical trends, so the alternative routing is only partial.

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