Skip to main content
Glama

get_price_movers

Segments (brand+model+fuel) whose median price moved most over ~30 days, filtered to credible moves (volume floors, 5–30% band, sample-stability guard). Each is annotated with a credibility-weighted moverScore (rewards volume and a stable sample over raw magnitude).

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
limitNoMax movers to return (default 25)
minNowNoMin listings in current snapshot (default 50)
countryNoMarket (default CZ)
minThenNoMin listings ~30 days ago (default 40)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "CZ",
      -  "SK",
      -  "DE",
      -  "AT",
      -  "PL",
      -  "HU",
      -  "RO",
      -  "LT",
      -  "LV",
      -  "NO"
      -]New value: +[
      +  "CZ",
      +  "SK",
      +  "DE",
      +  "AT",
      +  "PL",
      +  "HU",
      +  "RO",
      +  "LT",
      +  "LV",
      +  "NO",
      +  "BG"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "CZ",
      -  "SK",
      -  "DE",
      -  "AT",
      -  "PL",
      -  "HU",
      -  "RO",
      -  "LT",
      -  "LV"
      -]New value: +[
      +  "CZ",
      +  "SK",
      +  "DE",
      +  "AT",
      +  "PL",
      +  "HU",
      +  "RO",
      +  "LT",
      +  "LV",
      +  "NO"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "CZ",
      -  "SK",
      -  "DE",
      -  "AT",
      -  "PL",
      -  "HU",
      -  "RO"
      -]New value: +[
      +  "CZ",
      +  "SK",
      +  "DE",
      +  "AT",
      +  "PL",
      +  "HU",
      +  "RO",
      +  "LT",
      +  "LV"
      +]
  4. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the implicit filters (volume floors, 5–30% band, sample-stability guard) and explains that ranking is credibility-weighted rather than raw magnitude. What is missing is the shape of the response (fields per segment) and how the ~30-day window is anchored.

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?

Two dense sentences with the scope front-loaded and no filler; every clause carries substantive information about filtering or scoring. It is slightly jargon-heavy ('credibility-weighted moverScore') and packs several ideas per sentence, but nothing is wasted.

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?

For a four-parameter, all-optional query tool with no output schema and no annotations, the description covers both the selection logic and the ranking rationale, which is the hard part. Return-field detail and snapshot timing are absent, but the core decision-relevant behaviour is present.

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 four parameters are already fully documented with defaults and an enum for country. The description adds only indirect meaning — 'volume floors' maps loosely to minNow/minThen and '~30 days' to minThen's snapshot — without new syntax or constraints, so baseline 3 applies.

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 names a concrete resource (brand+model+fuel segments) and a concrete operation (rank by median-price movement over ~30 days), so an agent knows exactly what comes back. It does not, however, distinguish itself from near-neighbours such as get_price_history or get_market_trend, leaving that separation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for narrower or broader queries. The filtering and scoring details imply the intended 'top movers' use case, but with fifteen sibling tools in the family that inference is left entirely to the agent.

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