Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pricecharting_big_movers

Fetch PriceCharting's Big Movers report by category and sort order to identify products with significant signed price changes since the prior reading.

Instructions

Get PriceCharting's Big Movers report. Returns PriceCharting's Big Movers report for one category: the 100 products whose price changed most since the previous reading (the page says it is usually refreshed within the last week), with product id, name, console or set, address, current loose or ungraded price and the signed change. Choose the category (video-games, coins, comic-books, funko-pops, pokemon-cards, dragon-ball-cards, lorcana-cards, magic-cards, marvel-cards, one-piece-cards, star-wars-cards, yugioh-cards, garbage-pail-cards, other-tcg-cards, other-cards or lego-sets), the order (dollar-increase, dollar-decrease, percent-increase or percent-decrease) and, for video games, the region (all, japan, ntsc or pal). Price data is PriceCharting's; cite it with a link when you display it.

Input Schema

NameRequiredDescriptionDefault
sortNoOrder: dollar-increase (default), dollar-decrease, percent-increase or percent-decrease
regionNoRegion filter, video-games only: all (default), japan, ntsc or pal
categoryNoReport category; default video-games

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?

Without annotations, the description carries the burden well: it discloses the report size (100 products), data freshness ('refreshed within the last week'), the returned fields, and an attribution requirement ('cite it with a link'). It does not mention rate limits or auth, keeping it short of a 5.

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?

Front-loads the purpose and return contents before enumerating parameters. It is somewhat long due to listing all category values, but every element is functional and there is no filler.

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?

With no output schema and no annotations, the description explains what is returned and data freshness, which is the key missing context. It is nearly complete for a simple read-only report tool, though it omits invocation-sensitive details like auth or rate limits.

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% and all params are enums, so the schema already documents categories, order, and region. The description largely restates the same enum values and the video-games-only constraint, adding little beyond what the structured schema provides.

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 PriceCharting's Big Movers report') and elaborates on exactly what it returns: the 100 products whose price changed most, with named fields. An agent can distinguish it from siblings like pricecharting_price_history or pricecharting_product without opening a schema.

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?

Clearly frames how to invoke it (choose category, order, region) and scopes region to video games only. It gives solid context but does not explicitly compare against alternatives (e.g., alt_top_movers, google_finance_markets_movers) or state when not to use it.

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