Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

alt_top_movers

Get Alt card-market price movers as a cross-subject leaderboard, optionally filtered by category, or a specific player's per-category trend.

Instructions

Get Alt's biggest card-market price movers. Returns Alt's biggest price-index movers -- either a cross-subject leaderboard (optionally scoped to one category) or, when subject is set, that one player/character's own trend broken out per category it appears in. category is not strictly validated against alt-categories' list -- this trend index's own category set is broader (e.g. it includes MULTI-SPORT_CARDS).

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 50
subjectNoOptional exact player/subject name. Returns that subject's own trend per category instead of a leaderboard, and category is ignored.
categoryNoOptional category filter for the leaderboard. Ignored when subject is set. Omit to rank movers across every category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that category is not validated against alt-categories and that this index's category set is broader, but it omits return shape, pagination, and rate/size behavior beyond the schema's limit note.

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-loaded with the core purpose, then the two modes, then the caveat. Slightly redundant phrasing ('biggest card-market price movers' / 'biggest price-index movers') but overall tight and well-ordered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mode-switching tool with no output schema and no annotations, the description covers mode selection and one data caveat but says nothing about what a returned mover record contains. Adequate but leaves gaps an agent must discover empirically.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it clarifies the subject/category interaction and warns that the category value is not validated against alt-categories' taxonomy, which the schema does not state. This is genuine added semantic value.

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+resource ('Get Alt's biggest card-market price movers') and describes the two output modes (leaderboard vs subject trend). It is clear what the tool produces, though it does not explicitly name or differentiate itself from siblings like alt_market_trends.

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?

Explains the two operational modes and the condition that selects between them (subject set vs unset, category ignored when subject is set). Clear decision context, but no explicit exclusions against alternative tools or guidance on when this beats alt_market_trends.

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