Skip to main content
Glama

Market rates by pick-up day

get_market_rates
Read-onlyIdempotent

The car hire market at one airport this morning: for each car type and each of the next 14 pick-up days, the cheapest, lower-quartile and median (typical) advertised daily rate and the number of offers.

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_market_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
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_dateNoYYYY-MM-DD sweep (NZ date). Default latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description is not carrying the safety burden. It still adds real context beyond the annotations: data freshness ('this morning') and the exact 14-day forward window, which tells the agent this is a current, time-bounded projection rather than historical data. It does not state currency or whether rates include taxes/fees.

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?

A single dense sentence that front-loads the scope (one airport, this morning) then enumerates the returned statistics; nothing is redundant. The nested clause structure makes it slightly harder to parse than two shorter sentences would be.

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

Completeness4/5

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

With no output schema, describing the returned statistics was necessary, and the description does that well. All three parameters are documented in the schema, so the main remaining gaps are rate currency and how rates are composed, plus the missing sibling distinction.

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 explains airport codes, car type keys and sweep_date format; the baseline of 3 applies. The description adds that rates span 'the next 14 pick-up days', which clarifies how sweep_date anchors the window, but it introduces mild tension by saying 'for each car type' while an optional category parameter filters to a single type.

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 the resource precisely (car hire market rates at one airport) and even specifies the output granularity: one row per car type per pick-up day, with cheapest/lower-quartile/median rates and offer counts. An agent can tell what data comes back. It stops short of differentiating from close siblings such as get_market_snapshot or get_brand_rates.

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?

Usage is implied rather than stated: 'one airport' plus 'the next 14 pick-up days' signals a forward-looking, single-airport rate grid, which lets an agent infer when this fits. There is no explicit when-not guidance and no named alternative, so the agent must guess how this differs from the sibling snapshot/brand tools.

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