Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pricecharting_console

List products in a PriceCharting console or set, including IDs, images, and loose, complete, and new prices, with sorting and cursor pagination.

Instructions

List the products of a PriceCharting console or set. Lists the products of one PriceCharting console or set (for example a Pokemon set or a game console), 150 per page: id, name, product address, image and the loose/ungraded, complete/Grade 9 and new/PSA 10 prices. Sort by popularity, highest price, lowest price or name, and page with the returned cursor. Price data is PriceCharting's; cite it with a link when you display it.

Input Schema

NameRequiredDescriptionDefault
sortNoOrdering; defaults to popularity
cursorNoThe previous response's next_cursor; omit for the first page
consoleYesConsole or set slug from pricecharting-categories, for example pokemon-base-set or nes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the load and does it reasonably well: it discloses the 150-per-page cap, cursor-based paging, exactly which fields come back, and the three price tiers. It also adds a real behavioral obligation ('cite it with a link when you display it') that no structured field conveys. Read-only intent is only implied by 'List'.

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

Conciseness3/5

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

The first sentence ('List the products of a PriceCharting console or set') is immediately repeated and expanded by the second, so one sentence does redundant work. The rest is dense and front-loaded, packing fields, sort options, paging, and attribution efficiently.

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?

No output schema and no annotations, yet the description enumerates the returned fields, page size, sort options, and paging mechanism, which is what an agent needs to call it correctly. Missing only the upstream step of obtaining a valid console slug and any note on rate limits or error behavior.

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 the sort enum, cursor, and console slug are already fully documented. The description restates the sort options and paging rather than adding new meaning such as slug format rules or default-page behavior beyond what the schema provides; baseline 3 applies.

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 products of a PriceCharting console or set') with concrete examples of what a console/set is. It doesn't explicitly contrast itself with lookalike siblings such as pricecharting_search or pricecharting_product, so an agent must infer the distinction from the 'of a console' scoping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: pass a console/set slug and page through results. The description never says when to prefer this over pricecharting_search or pricecharting_big_movers, and the prerequisite (get the slug from pricecharting-categories) appears only in the schema, not the description.

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

Deploy Server

Other Tools