Skip to main content
Glama

Brand rates, ratings and position

get_brand_rates
Read-onlyIdempotent

Each rental brand at an airport this morning: price index vs market, share of days it's cheapest, median and cheapest daily rate per car type and pick-up day, customer rating with sub-scores, depot (in terminal, shuttle, distance), free-cancellation and automatic share.

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": {
      "airport": "<airport>"
    },
    "name": "get_brand_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoOptional brand name filter, e.g. Hertz, Sixt, Europcar.
airportYesIATA airport code, e.g. AKL, SYD, LHR, MAD. See list_airports.
categoryNoCar type key, e.g. compact, economy, suvs, intermediate, estate, fullsize, carriers_8. Car types: mini, economy, compact, intermediate, standard, fullsize, premium, luxury, suvs, estate, carriers_7, carriers_8, carriers_9, vans, pickups, convertibles (not every airport has every type).
sweep_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description need not restate it. What the description does add beyond annotations is the data-freshness framing ('this morning'), which is genuinely useful for interpreting results. It says nothing, however, about what happens when a brand or airport has sparse data, how 'market' is defined for the price index, or what granularity the per-pick-up-day breakdown takes.

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 dense sentence with no filler, and the airport-level per-brand framing comes first. The heavy comma-separated field enumeration is efficient but reads as a spec dump rather than prose, which slightly hurts scannability. Nothing is redundant enough to cut outright.

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?

With no output schema, the description bears the burden of explaining return values, and it does that well by enumerating the returned dimensions. But it leaves the sweep_date parameter and the notion of the snapshot window unexplained, and gives no sense of result cardinality (one row per brand? per brand per car type?). For a read-only aggregate tool of this breadth, it is adequate but has clear holes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description adds no parameter meaning whatsoever beyond echoing 'airport' and 'car type' implicitly through its field list. The one wholly undocumented parameter is sweep_date, which has an empty schema description and no mention in the text — and it is precisely the parameter that would define the 'this morning' snapshot the description leans on. That is a substantive gap the description does not compensate for.

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 makes the resource concrete: per-brand aggregates for every rental brand at a given airport — price index vs market, cheapest-day share, median/cheapest daily rates by car type and pick-up day, ratings with sub-scores, depot info, and cancellation/automatic share. It is a field enumeration rather than a verb phrase, and it never distinguishes itself from close siblings like get_brand_position, get_market_rates, or get_ratings, so an agent cannot confidently route between them without guessing.

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?

There is no when-to-use guidance, no when-not-to-use, and no named alternative. The sibling set contains at least three tools whose surface overlaps strongly (get_brand_position, get_market_rates, get_ratings), and the description offers nothing to disambiguate them. The only usage-adjacent signal is the phrase 'this morning', which implies a snapshot rather than historical query, but that is inference, not guidance.

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