Skip to main content
Glama

get_market_overview

Comprehensive market snapshot for a country: price pulse and direction, buyer/seller verdict, fuel & body-type & brand breakdowns, deal hotspots, 90d price trend, supply/freshness, oversupply and fast-mover signals.

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

Input Schema

NameRequiredDescriptionDefault
countryNoMarket (default CZ)

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

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

No annotations are supplied, so the description carries the full burden, and it does disclose the substance of what the call returns — verdicts, breakdowns, hotspots, 90-day trends, supply/freshness, oversupply and fast-mover signals — which implies a read-only analytical retrieval with no mutation. It stops short of stating cost, caching, latency, or data freshness guarantees.

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?

It is a single front-loaded sentence fragment that fronts the purpose before listing contents, with no filler sentences. It is dense with domain jargon ('price pulse', 'buyer/seller verdict', 'fast-mover') whose precise meaning is not glossed, which slightly reduces clarity for an unfamiliar agent.

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 single-optional-parameter, read-only aggregate tool with no annotations or output schema, the description gives a solid inventory of the returned metrics so the agent knows what a call yields. The main gaps are the absence of any routing guidance versus the many sibling tools and no statement of return shape or units.

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?

With one parameter at 100% schema description coverage (an enum of market codes with a documented CZ default), the schema already does the semantic work. The description adds only the framing 'for a country', which confirms the parameter's role but supplies no extra detail such as whether markets share a currency or data cadence.

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 opens with a specific verb+resource combination ('Comprehensive market snapshot for a country') and then enumerates the exact contents: price pulse/direction, buyer/seller verdict, breakdowns, deal hotspots, 90d trend, supply/freshness, oversupply and fast-mover signals. This makes the tool's scope clearly broader than point tools like get_market_trend or get_price_history, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The word 'Comprehensive' plus the aggregate list of contents implies this is the broad orientation tool to reach for when a general country-level picture is needed, but there is no explicit when-to-use statement and no named alternative (e.g. get_market_trend, get_weekly_summary, get_price_movers) for narrower questions. Usage must be inferred from the enumerated contents.

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