Crawlora MCP

pricecharting_console

Read-only

List the products of one PriceCharting console or set (for example pokemon-base-set or nes), 150 per page: id, name, product address, image and loose/ungraded, complete/Grade 9 and new/PSA 10 prices. Sort by popularity, highest price, lowest price or name and page with next_cursor. Find console slugs with pricecharting_categories.

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": {
      "console": "<console>"
    },
    "name": "pricecharting_console"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Ordering; defaults to popularity. Documented values: popularity, highest-price, lowest-price, name.
`cursor`	No	The previous response's next_cursor; omit for the first page
`console`	Yes	Console or set slug from pricecharting-categories, for example pokemon-base-set or nes

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful operational context: 150 results per page and pagination via next_cursor. It does not mention rate limits or caveats about external price data, but it adds meaningful behavior beyond 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.

Conciseness5/5

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

The description is front-loaded with the core action and then supplies examples, return fields, sort options, pagination, and the slug prerequisite. It is dense but appropriately sized, with no wasted sentences.

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?

Given the output schema, annotations, and complete parameter schema, the description provides everything essential for correct invocation: what it lists, where the required console slug comes from, sort options, page size, and pagination. No critical context is 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 description coverage is 100%, so the schema already documents console, sort, and cursor semantics. The description reinforces examples and sort values but does not add substantial meaning beyond the structured schema.

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: list products for one PriceCharting console or set. It gives concrete examples ('pokemon-base-set or nes') and clearly distinguishes this from discovery of console slugs by naming 'pricecharting_categories'.

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?

It clearly explains the prerequisite for obtaining a console slug via 'pricecharting_categories' and describes sorting and pagination options. It does not explicitly exclude using this tool when a product-level lookup or search would be better, so it falls short of full when/when-not guidance.

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

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