Skip to main content
Glama

Biggest movers

movers
Read-onlyIdempotent

Use this when the user asks which cards in one game rose or fell the most recently. Returns the biggest percentage moves over the last days (1 to 90) for cards worth $5 or more, with the start and end market price in USD. Describes past moves only; not a prediction.

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": "movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window, 1 to 90 days.
gameNoCard game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world.pokemon
limitNo1 to 100.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam."New value: +"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world."
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "pokemon",
      -  "one-piece",
      -  "lorcana",
      -  "riftbound",
      -  "yugioh",
      -  "gundam"
      -]New value: +[
      +  "pokemon",
      +  "one-piece",
      +  "lorcana",
      +  "riftbound",
      +  "yugioh",
      +  "gundam",
      +  "fusion-world"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window, 1 to 90 days."
    • addedInput schema / properties / game / description
      Added value: +"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam."
    • addedInput schema / properties / game / enum
      Added value: +[
      +  "pokemon",
      +  "one-piece",
      +  "lorcana",
      +  "riftbound",
      +  "yugioh",
      +  "gundam"
      +]
    • addedInput schema / properties / limit / description
      Added value: +"1 to 100."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the description's job is to add substance beyond that — and it does: a $5 minimum price filter, a 1–90 day window, and returned start/end market prices in USD. It stops short of describing ordering/ties or whether risers and fallers are returned together.

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 short sentences, front-loaded with the trigger condition before the output description and the past-only caveat. The parenthetical '(1 to 90)' duplicates the schema's own range, a small redundancy in an otherwise tight definition.

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?

An output schema exists, so return values need no full explanation, and the annotations plus the $5 floor and window bounds cover the essentials for a simple three-parameter read tool. The one material gap is what 'limit' actually bounds when both risers and fallers exist.

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%, so the schema already documents days (1–90), the game enum, and limit (1–100); the description repeats the days range but adds no new meaning. It is silent on how limit interacts with direction — e.g. whether it caps risers and fallers individually or combined.

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: 'which cards in one game rose or fell the most recently', with scope ($5+ cards, percentage moves, USD prices). It implicitly separates itself from all_time_highs/all_time_lows by emphasizing a recent look-back window, though it never names those siblings directly.

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?

Opens with an explicit trigger ('Use this when the user asks which cards... rose or fell the most recently') and adds a clear exclusion ('Describes past moves only; not a prediction'). It does not point to competing tools such as price_history or most_valuable when the user wants a trend chart or an absolute ranking rather than a percentage move.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources