Skip to main content
Glama

list_models

Models for a given brand that currently have active deals, with counts.

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

Input Schema

NameRequiredDescriptionDefault
brandYesBrand name (required)
fuelsNoFuel types, e.g. ["diesel","benzín","elektro","hybrid"]
yearMaxNo
yearMinNo
priceMaxNoMaximum price in CZK
priceMinNoMinimum price in CZK
bodyTypesNo
countriesNoMarkets to include (default CZ)
maxMileageNoMaximum mileage in km
minDiscountNoMinimum % below market median (e.g. 20)
priceDroppedNoOnly listings whose price recently dropped

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / countries / items / 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 / countries / items / 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 / countries / items / 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that only models with active deals are returned and counts are included, but says nothing about permissions, pagination, sorting, empty results, or how optional filters affect the response.

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?

The description is a single front-loaded sentence fragment with no wasted words. It is concise, but its terseness leaves important behavior implicit.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no annotations and no output schema, one sentence is not enough. The definition omits filter semantics, defaults, pagination, return shape, and error behavior.

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?

The schema has 73% description coverage across 11 parameters, so most parameter meaning comes from the schema itself. The description reinforces the required brand scope and the active-deals filter, but it does not clarify yearMin/yearMax, bodyTypes, or how multiple filters interact.

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 specific resource (models), scope (for a given brand), and condition (currently active deals, with counts). It is clearly distinguishable from a brands list, though it does not explicitly name when to prefer a sibling like search_deals.

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?

It implies the tool is for viewing models with active deals for a brand, but gives no explicit when-to-use guidance, no alternatives, and no prerequisites. An agent must infer the choice between this and deal-search siblings.

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