Skip to main content
Glama

disruption_triage

Assess whether an airport is currently disrupted by combining weather, traffic and movement data into one advisory severity report with reasons and explicit unknowns.

Instructions

Assess whether an airport is currently disrupted: weather, traffic, movements.

This is the composite tool an agent should reach for first. It makes one
weather call (free), one movements call per direction and one traffic call
(OpenSky credits), then reports severity together with its reasons and its
unknowns. Severity is advisory only.

Args:
    airport: ICAO code, e.g. ESGG.
    radius_nm: Traffic search radius in nautical miles (5-200).

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

Input Schema

NameRequiredDescriptionDefault
airportYes
radius_nmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it delivers notable behavioral context: relative cost of the underlying calls (weather free, traffic consumes OpenSky credits), that severity is advisory only, and that the result explicitly reports its own unknowns. It does not cover failure modes, throttling, or partial-result behavior, but the cost and advisory caveats are exactly the kind of disclosure an agent needs before invoking it.

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 description is front-loaded: the one-line purpose comes first, then the routing recommendation, then cost and caveats, then arguments. The Args block is compact and every sentence contributes information; the only mild slack is the line break introduced between the purpose sentence and the composite-tool sentence.

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?

For a composite tool over several upstream services, the description covers the essential concerns: what it aggregates, the cost asymmetry between underlying calls, that severity is advisory, and that unknowns are surfaced. Since an output schema exists, return-value structure need not be restated, and the parameter documentation compensates for the zero schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: airport is defined as an ICAO code with a concrete example (ESGG), and radius_nm is given meaning as a traffic search radius in nautical miles bounded to 5-200. The default of 40 is left to the schema, which is acceptable since the schema declares it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: assess whether an airport is currently disrupted, covering weather, traffic, and movements. It explicitly positions itself as the composite entry point an agent should try first, which distinguishes it from the single-domain siblings (airport_weather, airport_movements, airport_live_traffic) without needing to name them.

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?

There is clear usage context: it is the first tool to reach for, and it explains the internal composition (one weather call, one movements call per direction, one traffic call). What is missing is explicit when-not guidance, e.g. that an agent should call the individual weather or movements tools when it only needs one data source or wants to avoid OpenSky credit spend.

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