Skip to main content
Glama

Get typical asking price

get_model_price
Read-onlyIdempotent

Use this when the user asks how much a car model costs in Slovakia, or whether a price for a model is reasonable. Returns the median ASKING price of the brand/model (optionally one model year) in AutoIsto's current offer, the sample size, the price range and the date. The median is omitted below 20 cars with a plain price. These are prices sellers ask, not sale prices; mileage and equipment move the price, so present it as a guide. Do not use it for valuing a specific car's condition, for new-car prices or for markets outside Slovakia.

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>"
    },
    "name": "get_model_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoModel year, only together with model.
brandYesCar brand, e.g. Škoda, Volkswagen, BMW (abbreviations such as VW work).
modelNoModel, e.g. Octavia, Golf, X5, Rad 3, C trieda (English names such as 3 Series or C-Class also work — the interpretation is returned). Versions, body variants and generations (RS, Variant, B8) are not separated: figures cover the whole model and notApplied says so. Omit for the whole brand.

Output Schema

NameRequiredDescriptionDefault
urlYesModel page on www.autoisto.sk.
asOfYesDate of the figures (YYYY-MM-DD).
noteYes
yearYes
brandYes
foundYes
modelYes
scopeYesWhat the figures cover. "brand" when no model was given — a year is applied only together with a model, see note.
notAppliedYesPart of the requested model the figures do NOT reflect (version, body, generation, e.g. "RS", "Variant", "B8"): figures cover the whole model. Tell the user.
sampleSizeYesCars the median is computed from.
listedCountYesCars of this brand/model(/year) in the offer today.
maxPriceEurYes
minPriceEurYes
interpretationYesHow the model name was understood when AutoIsto knows it under another name ("3 Series" → Rad 3, "320d" → Rad 3). Tell the user.
medianAskingPriceEurYesMedian ASKING price; null when fewer than 20 cars have a plain price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the median is suppressed below 20 cars with a plain price, that returned figures are asking not sale prices, that mileage and equipment move the price, and that the response carries sample size, range and date. These are exactly the caveats an agent needs to avoid overclaiming precision.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case, then output shape, then caveats, then exclusions — three tight sentences and a closing prohibition, with no filler. Every clause carries actionable content.

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?

Even though an output schema exists (so return details are optional), the description still names the returned fields and the small-sample suppression rule, closing the one gap an output schema could not convey. 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 coverage is 100% and already documents brand, model and the year-needs-model constraint, so the schema carries the load. The description adds only a light touch ('optionally one model year') and does not extend the aggregation/version caveat beyond what the model field description already states.

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 specific verb+resource with explicit scope: the median ASKING price of a brand/model (optionally one year) from AutoIsto's current Slovak offer. The 'asking, not sale price' framing and the Slovakia-only scope make it impossible to confuse with get_car_details or search_cars.

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?

Explicit when-to-use ('user asks how much a car model costs in Slovakia, or whether a price is reasonable') paired with explicit exclusions ('not for valuing a specific car's condition, new-car prices or markets outside Slovakia'). The exclusions functionally route the agent away from the sibling get_car_details.

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