Skip to main content
Glama

Compare airports

compare_airports
Read-onlyIdempotent

Rank airports by real cost (car only / with driver / with cover), typical deposit, debit-card friendliness or late desk hours. Use for 'where in Spain is car hire cheapest in March?' or 'which airport is best for a debit card?'

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many airports to return (default 10).
monthNoOptional pick-up month YYYY-MM (price sort uses that month)
countryNoOptional country to compare within
sort_byNoWhat to rank by: price (car only), price_with_driver, price_with_cover, deposit (lowest first), debit (most debit-friendly), late_desk (open latest). Default price.
airportsNoOptional list of airports

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNo
airportsNo
sorted_byNo
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / provenance
      Added value: +{
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many airports to return (default 10)."
    • addedInput schema / properties / sort_by / description
      Added value: +"What to rank by: price (car only), price_with_driver, price_with_cover, deposit (lowest first), debit (most debit-friendly), late_desk (open latest). Default price."
  3. First observed

TDQS

A3.8/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 without description support. The description adds only that price sorting is month-dependent, which is closer to parameter semantics than behavior; it says nothing about result size limits beyond what the schema states or how ties/absent data are handled.

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

Conciseness5/5

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

Two tight sentences: the ranking dimensions come first, the disambiguating example queries second. Every parenthetical carries information about what 'cost' actually means, and there is no filler or repetition of the title.

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 an output schema present, rich annotations and full schema coverage, the description only needs to convey purpose and ranking semantics, which it does. The remaining gap is that it never positions the tool against airport_costs or list_airports, leaving the agent to infer which sibling to pick for a single-airport lookup.

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% and the sort_by enum is documented field-by-field, so the schema does the heavy lifting and a 3 is the baseline. The description's parenthetical glosses ('car only / with driver / with cover', 'late desk hours') mirror the enum rather than add new meaning, and it does not explain the interaction between month and non-price sort modes or how the optional airports list combines with country.

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 opens with a specific verb (Rank) and resource (airports) and enumerates the exact metrics ranked — real cost tiers, deposit, debit friendliness, late desk hours — so the agent knows precisely what the output ordering means. It stops short of differentiating itself from the sibling airport_costs, which likely returns costs for a single airport, so sibling disambiguation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use for...' framing plus two concrete natural-language question examples ('where in Spain is car hire cheapest in March?', 'which airport is best for a debit card?') give a clear sense of when this tool is the right call. There are no explicit when-not conditions or named alternatives, so it sits just below the top band.

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.