Skip to main content
Glama

Compare airports

compare_airports
Read-onlyIdempotent

One car type across all (or chosen) airports this morning: median and cheapest daily rate over the next 14 pick-up days in NZD and local currency, and offer depth.

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": {
      "category": "<category>"
    },
    "name": "compare_airports"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportsNoOptional list of codes.
categoryYesCar 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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: the data is a morning snapshot, the horizon is the next 14 pick-up days, and results are dual-currency (NZD plus local). Those freshness and coverage details matter for interpreting rates, though 'offer depth' is left unexplained.

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

Conciseness3/5

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

It is a single sentence with no filler, so nothing is wasted, but the density borders on cryptic — 'offer depth' and the trailing currency clause require unpacking. Front-loading the car-type-across-airports scope works well.

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, the description carries the burden of describing returns and does so: median rate, cheapest rate, 14-day horizon, both currencies. The main residual gap is the undefined 'offer depth', which leaves one returned metric ambiguous.

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%, so both parameters are already documented with examples and a full car-type list. The description adds only the framing that airports may be all or a chosen subset, which the schema's 'Optional list of codes' largely already conveys.

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?

States a specific resource and scope: one car type compared across all or selected airports, returning median and cheapest daily rates. It is clearly a cross-airport rate comparison rather than a brand- or market-level lookup, so it is separable from siblings like get_brand_rates and get_market_rates, though the verb is nominal rather than explicit.

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: a single category swept over airports, with the 'airports' parameter noted as optional for narrowing scope. There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named for single-airport or per-brand queries.

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