Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pricecharting_search

Search PriceCharting's price guide for trading cards, video games, comics, coins, Funko Pops, LEGO and more to get up to 100 matches with product details and loose, complete, and new prices.

Instructions

Search PriceCharting products. Searches PriceCharting's price guide (trading cards, video games, comics, coins, Funko Pops, LEGO and more) and returns up to 100 matches: product id, name, console or set, category, image and the loose/ungraded, complete/Grade 9 and new/PSA 10 prices. Narrow by console_uid, drop variants, and sort by popularity, highest price or name. Price data is PriceCharting's; cite it with a link when you display it.

Input Schema

NameRequiredDescriptionDefault
qYesSearch text, 2 to 100 characters
sortNoOrdering; defaults to popularity
console_uidNoRestrict to one console or set by its console_uid (for example G10623), as returned in search results and by pricecharting-console
exclude_variantsNoDrop variant printings such as 1st Edition

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the 100-result cap, enumerates the returned fields including the three price tiers, and states an attribution obligation ('cite it with a link'). It does not cover rate limits, auth, or pagination beyond the cap, but the important behavioral traits are present.

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?

Three front-loaded sentences with no filler; the corpus scope and result shape come first, followed by filter/sort options and the attribution note. Dense but every clause contributes.

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 exists, so the description correctly compensates by describing the returned fields and the 100-item cap; no annotations means safety is a non-issue for a read-only search. The only real gap is whether results beyond 100 are reachable, which is moot since the schema has no paging parameters.

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 baseline is 3. The description restates the same knobs (console_uid narrowing, dropping variants, sort order) without adding format or edge-case detail beyond the schema, such as what a console_uid looks like or how 'popularity' is computed.

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 ('Search PriceCharting products') and immediately scopes the corpus (trading cards, video games, comics, coins, Funko Pops, LEGO), which distinguishes it from the sibling detail/console/category tools without naming them.

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?

Usage context is clear: this is the entry point for finding products, with narrowing via console_uid, variant exclusion, and sorting called out. It stops short of explicitly routing to pricecharting_product or pricecharting_price_history for follow-up detail, so there is no explicit when-not-to-use guidance.

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