Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

pricecharting_big_movers

Read-only

Get PriceCharting's Big Movers report for one category: the 100 products whose price changed most since the previous reading, with product id, name, console or set, address, current loose or ungraded price and the signed change in dollars or percent. Choose the category (video games, coins, comics, Funko Pops, Pokemon, Magic, Yu-Gi-Oh, One Piece, Lorcana, LEGO and more), the order (dollar or percent, increase or decrease) and, for video games, a region. Use this to see which collectibles are moving. Price data is PriceCharting's; cite it with a link.

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_big_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder: dollar-increase (default), dollar-decrease, percent-increase or percent-decrease. Documented values: dollar-increase, dollar-decrease, percent-increase, percent-decrease.
regionNoRegion filter, video-games only: all (default), japan, ntsc or pal. Documented values: all, japan, ntsc, pal.
categoryNoReport category; default video-games. Documented values: 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, lego-sets.

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

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

Annotations already declare readOnlyHint and openWorldHint. The description adds that the data is PriceCharting's and should be cited with a link, which is a useful attribution requirement not captured by annotations. It also describes the response fields (product id, name, console/set, address, price, change).

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?

The description is front-loaded with the core purpose, then moves to parameter selection and a citation note. It is efficient with no obvious waste, though it could be slightly tighter by merging the parameter explanation into the first sentence.

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 exists, the description needn't explain return values. Annotations cover safety (read-only) and scope (open-world). The description covers what the tool does, how to configure it, and a usage note about citation. Nothing critical is missing for a read-only report tool.

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 schema already documents all three parameters fully. The description adds some natural-language examples (e.g., category names like video games, coins, comics; order meanings) and clarifies that region applies only to video games, but this is marginal value beyond the schema.

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?

The description gives a specific verb and resource: 'Get PriceCharting's Big Movers report for one category', and even details the report's contents (100 products, fields). It is not a tautology or vague. However, it does not explicitly differentiate itself from sibling tools like pricecharting_price_history or pricecharting_product, which keeps it at a 4.

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 provides clear context with 'Use this to see which collectibles are moving' and explains the parameters to choose. There are no explicit exclusions or named alternatives, but the intended use case is adequately communicated.

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