Skip to main content
Glama
Sign In

Gaduin

by com.gaduin
OverviewDiscussionsAdmin

Flight status

get_flight_status
Read-onlyIdempotent

Live status of a flight by number (e.g. BA117 or BAW117). Returns the canonical flight number, the leg in the air or next to depart (or the most recent one), its departure and arrival times in UTC and airport-local time with the time zone, delay in minutes, the last update time, a link to the flight page on gaduin.com and, when one is open, a link to the prediction market on that journey.

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": {
      "number": "<number>"
    },
    "name": "get_flight_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesFlight number: airline IATA or ICAO code plus number, e.g. BA117.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, so the description isn't burdened with safety disclosure. It still adds real value beyond them by disclosing the selection fallback ('the leg in the air or next to depart (or the most recent one)') and what the last-update time means. It does not say what happens when the flight number is unknown or invalid, which keeps it below 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?

One front-loaded sentence that identifies the tool and its inputs before enumerating outputs; every clause carries information. The trailing enumeration of returned fields is long but justified by the absence of an output schema.

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 usefully enumerates the return payload: canonical number, leg, UTC and local times with time zone, delay minutes, last update, and links. Gaps remain around error/not-found behavior and whether results are cached or real-time beyond the word 'Live'.

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% and the schema already states 'airline IATA or ICAO code plus number, e.g. BA117'. The description adds one extra example (BAW117) but no additional constraint, validation behavior, or normalization detail, so the baseline 3 applies.

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 verb+resource: 'Live status of a flight by number', with concrete format examples (BA117 or BAW117). It implicitly distinguishes live status from the sibling get_flight_history by the word 'Live', but never names or contrasts with any sibling, so it falls short of 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 only implied by 'Live status' — an agent can infer this is for current/upcoming flights rather than historical ones, but there is no explicit when-to-use or when-not, and no routing to get_flight_history, search_flights, or get_station_board.

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