Skip to main content
Glama
iwantmymtg-mcp

iwantmymtg-mcp

get_price_movers

Read-only

Track Magic: The Gathering card price rises and falls over 7 days, showing current and prior prices plus dollar and percent changes; filter by set, rarity, type, format, or finish.

Instructions

The week's biggest Magic: The Gathering price moves: the cards whose price rose (direction 'up', the default) or fell (direction 'down') the most over the last 7 days, one row per printing and finish, with today's price, the price a week ago, and the change in dollars and percent. Ranked by percent unless by is 'amount'. Cards worth less than minPrice (default $5) both before and after the move are left out, and so are prices that jumped back and forth during the week, which come from a missing vendor price rather than a real move. Narrow it with setCode, rarity, type, format legality or finish.

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

Input Schema

NameRequiredDescriptionDefault
byNoRank by 'percent' change (default) or dollar 'amount'.
pageNo1-based page index.
typeNoSubstring match against card type line (e.g. 'Goblin', 'Instant').
limitNoPage size (max 100).
finishNoOnly this finish. Both by default.
formatNoFilter to cards with a legality entry in this format (e.g. 'modern', 'commander').
rarityNoFilter by rarity.
setCodeNo3-5 character set code (e.g. 'lea', 'mh3').
legalityNoUsed with 'format'. Defaults to 'legal' when format is set.
minPriceNoIgnore cards worth less than this many dollars both before and after the move. Defaults to 5.
directionNo'up' for the biggest increases (default), 'down' for decreases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest — and it does, disclosing the output row fields, the exclusion of low-value cards, and the non-obvious data-quality caveat that whipsaw prices come from missing vendor prices rather than real moves. It does not cover pagination or result-count behavior, keeping it from 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?

A single dense paragraph that leads with what the tool returns and front-loads defaults and exclusions. Every clause carries information, though the run-on construction makes it slightly harder to scan than a short bulleted breakdown would be.

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 11 optional parameters and no output schema, the description does the heavy lifting on return shape — today's price, last week's price, dollar and percent change — plus the filtering and exclusion model. What remains unstated, such as total-count or tie-breaking behavior, is minor for an agent deciding how to call it.

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 every parameter is already documented in the schema. The description largely restates those defaults (direction, by, minPrice) and mentions the filter dimensions by name without adding syntax or edge-case meaning beyond the schema; baseline 3 applies.

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 concrete verb and resource — the week's biggest price moves — plus the exact scope (7 days, one row per printing and finish, ranked by percent unless overridden). An agent can distinguish it from get_card_price_history or get_card_performance without opening any 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?

The description makes the default direction ('up'), the default ranking ('percent'), and the default floor ('$5') explicit, and lists the axes for narrowing results. It stops short of naming a sibling alternative or stating when this tool should NOT be used instead of the per-card history tools.

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