Skip to main content
Glama

Desks open

desks_open
Read-onlyIdempotent

Which car-hire desks at an airport are still open when the person lands: each company's own measured closing time, sorted into open / closes within 45 minutes of landing / already closed, the 24-hour desks, the typical late pick-up fee and a search link timed to reach the desk. Use for late or night flights ('we land at 23:40, who is still open?').

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

Input Schema

NameRequiredDescriptionDefault
airportYesAirport id, IATA code or name, e.g. 'faro', 'FAO', 'Faro Airport'
arrival_timeNoOptional landing time, local, e.g. 23:40. Without it: every company's closing time, latest first.

Output Schema

NameRequiredDescriptionDefault
iataNo
noteNo
errorNo
airportNo
open_24hNo
report_urlNo
search_linkNo
arrival_timeNo
closed_by_thenNo
late_pickup_fee_typicalNo
closing_times_latest_firstNo
open_when_you_reach_the_deskNo
closes_within_45_min_of_landingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: closing times are 'each company's own measured' values and results are bucketed into open / closes within 45 minutes of landing / already closed, which tells the agent how to interpret and present results. Minor gaps remain (no pagination or coverage caveats), which keeps it from a 5.

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 sentences, both front-loaded with the core question before the output inventory and the usage example. The first sentence is long and list-like but nearly every clause carries distinct information. No filler or marketing language.

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?

Because an output schema exists, the description does not need to enumerate return fields, and it correctly spends its words instead on the bucketing logic, the data's provenance ('measured closing time'), and the intended scenario. An agent has enough to decide and call correctly; only explicit sibling routing is absent.

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 both parameters are documented there, including the no-arrival_time fallback ('every company's closing time, latest first'). The description re-frames arrival_time as 'when the person lands' and motivates the 45-minute bucket, but adds no syntax or format detail the schema lacks. Baseline 3 is appropriate.

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 a precise question it answers: 'which car-hire desks at an airport are still open when the person lands', and enumerates what comes back (open/closing/closed buckets, 24-hour desks, late pick-up fee, timed search link). That is far more than a restatement of the name. It does not name any sibling (e.g. build_search_link, which clearly overlaps with the 'search link' output), so it stops short of full sibling differentiation.

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?

Gives explicit context for use — 'Use for late or night flights' — with a concrete example query ('we land at 23:40, who is still open?'). There are no stated exclusions or named alternatives, so the agent must infer that non-late-flight scenarios belong elsewhere, but the positive guidance is clear.

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.