Skip to main content
Glama
Sign In

Gaduin

by com.gaduin
OverviewDiscussionsAdmin

Airport status today

get_airport_status
Read-onlyIdempotent

How an airport is running today (airport-local day): its status (severe, disrupted, normal, quiet or no_data), disruption score (0-1, the worse side), which side is worse, and for departures and arrivals the flights scheduled, completed, delayed and cancelled, the delayed, cancelled and disrupted shares and the median delay of the delayed ones, with a link to the airport page on gaduin.com.

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

Input Schema

NameRequiredDescriptionDefault
airportYesAirport IATA code (e.g. LHR) or ICAO code (e.g. EGLL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world, idempotent, non-destructive operation. The description adds meaningful behavior beyond that: it discloses the five possible status values, the 0-1 disruption-score range and its 'worse side' semantics, the per-direction breakdown of scheduled/completed/delayed/cancelled counts, derived shares, median delay of delayed flights, and an outbound link to gaduin.com.

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?

The definition is one dense but front-loaded sentence that begins with the core purpose and then enumerates returned fields. Every clause conveys substantive information, though the run-on structure makes it slightly harder to scan than a short lead sentence plus itemized details.

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

Completeness5/5

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

Given a single fully documented parameter, rich annotations, and no output schema, the description thoroughly covers what the tool returns: status values, score semantics, directional breakdowns, derived shares, delay median, and an external link. Nothing an agent needs in order to call or interpret this tool appears to be missing.

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?

The single 'airport' parameter is fully documented in the schema with both IATA and ICAO examples (100% coverage), so the schema carries parameter meaning. The description adds nothing further about the parameter, which is consistent with the baseline for high schema coverage.

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 states a specific retrieval target (an airport's status for the current airport-local day) and enumerates the exact metrics returned, so the agent knows precisely what this tool produces. It does not explicitly contrast itself with siblings such as get_station_board or list_disrupted_airports, which keeps it from a 5.

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 by the phrase 'How an airport is running today' and the airport-local day scoping, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for related needs like a station board or a list of disrupted airports.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gaduin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources