Skip to main content
Glama

Get typical price of a model year

get_model_price
Read-onlyIdempotent

Use this when the user asks how much a car model of a given year costs in the Czech Republic, or whether a price for it is reasonable. Returns, for one brand, model and model year: the median ASKING price in AutoIsto's current offer (any mileage) and the median LAST price at which such cars left the offer, each with its sample size, and the month. A figure is omitted when its sample is too small. Asking prices are what sellers ask, not sale prices, and a car leaving the offer is not proof of a sale; mileage and equipment move the price, so present it as a guide. Requires a year; if the user did not give one, ask. Do not use it for valuing a specific car's condition, for new-car prices or for markets outside the Czech Republic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand": "<brand>",
      "model": "<model>",
      "year": "<year>"
    },
    "name": "get_model_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesModel year.
brandYesCar brand, e.g. Škoda, Volkswagen, BMW (abbreviations such as VW work).
modelYesModel, e.g. Octavia, Golf, X5, Řada 3, Třída C (English names such as 3 Series or C-Class also work — the interpretation is returned). Versions, body variants and generations (RS, Combi, B8) are not separated: figures cover the whole model and notApplied says so.

Output Schema

NameRequiredDescriptionDefault
urlYesSearch for this model and year on www.autoisto.cz.
noteYes
yearYes
brandYes
foundYes
modelYes
monthYesMonth the figures are for (YYYY-MM, Prague time).
notAppliedYesPart of the requested model the figures do NOT reflect (version, body, generation, e.g. "RS", "Combi", "B8"): figures cover the whole model. Tell the user.
exitSampleSizeYes
interpretationYesHow the model name was understood when AutoIsto knows it under another name ("3 Series" → Řada 3, "C-Class" → Třída C). Tell the user.
askingSampleSizeYes
medianExitPriceCzkYesMedian of the LAST price at which cars of this model and year left AutoIsto's offer (removed from the offer — not necessarily sold); null when too few.
medianAskingPriceCzkYesMedian ASKING price of this model and year in today's offer (any mileage); null when the sample is too small.
exitPriceLowerQuartileCzkYes
exitPriceUpperQuartileCzkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-open-world), so the description carries the substantive behavioral burden and does: it discloses that figures are omitted when samples are too small, that asking prices are not sale prices, that leaving the offer is not proof of a sale, and that mileage/equipment affect the figure. This is exactly the kind of caveat an agent needs to present results honestly.

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?

Dense and mostly front-loaded: trigger, then output contents, then caveats, then exclusions. Every sentence earns its place, but the single long paragraph packs return contents, caveats and exclusions together and could be slightly tighter for scanning.

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

Completeness5/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 not be explained, yet the description still tells the agent which fields come back (median asking, median last, sample size, month) and how to frame them. Combined with the required-parameter rule and market scope, nothing needed to call it correctly is missing.

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 brand, model and year, including the model-variant collapsing note. The description reinforces the year requirement and the 'any mileage' scope of the asking price but adds no syntax or format detail beyond the schema, so the 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 precise verb+resource+scope: the median asking price and median last price for one brand/model/model-year in the Czech Republic. The scope constraints (whole-model aggregate, one year, Czech market only) implicitly separate it from search_cars and get_car_details, which deal with individual listings/details.

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

Usage Guidelines5/5

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

Opens with an explicit trigger phrase ('Use this when the user asks how much...or whether a price is reasonable') and closes with explicit exclusions (not for a specific car's condition, new-car prices, or non-Czech markets). It also states the prerequisite: a year is required, and the agent should ask the user if missing.

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