Skip to main content
Glama

list_brands

Brands that currently have active deals, with deal counts. Accepts the same filters as search_deals.

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

Input Schema

NameRequiredDescriptionDefault
fuelsNoFuel types, e.g. ["diesel","benzín","elektro","hybrid"]
yearMaxNo
yearMinNo
priceMaxNoMaximum price in CZK
priceMinNoMinimum price in CZK
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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the key behavioral trait that only brands with currently active deals are returned and that counts accompany each brand, but it says nothing about ordering, result limits, or whether counts reflect all deals or only filtered ones.

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 short sentences, front-loaded with the resource and the active-deal constraint, with zero filler. Slight deduction for the verbless fragment opening, which reads more like a caption than a directive.

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

Completeness3/5

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

For a 9-parameter, zero-annotation tool with no output schema, the definition is thin: aggregation semantics (brand-level rollup, count definition, ordering) and return shape are left unspecified. It covers the essentials for selection but not for confident invocation.

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 78%, so the schema already documents most filter parameters including units (CZK, km, % below median). The description's only parameter content is a cross-reference to search_deals, which adds no semantics of its own; 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?

Identifies the resource (brands) and the scoping condition (only brands with currently active deals), plus the added payload (deal counts), which is enough to distinguish it from search_deals, which returns listings. The phrasing is a noun fragment with no explicit verb, but the intent is unambiguous.

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 line 'Accepts the same filters as search_deals' implies this is the brand-level aggregation counterpart to the deal search, so an agent can infer 'use this when you want brand rollups, not listings.' However, it never states that explicitly, gives no when-not guidance, and doesn't say what happens when filters yield no matching deals.

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