Skip to main content
Glama

UK Data for Agents

pireps_near_airport

Read-onlyIdempotent

Recent pilot reports (PIREPs) within a distance of an airport: turbulence and icing with intensity, altitude, aircraft type and time, plus a tally of how many reports found none, light, moderate or severe turbulence. PIREPs are the only first-hand reports of turbulence actually encountered, so they answer "is it bumpy around Denver right now" for pilots and nervous flyers. Source: NOAA/NWS Aviation Weather Center; coverage is mainly the United States. Reports are sparse and individual; not for flight planning. (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
icaoNostring, required, ICAO airport code at the centre of the search (e.g. KDEN)
limitNointeger, optional, reports to list (newest first), 1-100, default 25
age_hoursNointeger, optional, how far back to look in hours, 1-24, default 3
distance_nmNointeger, optional, radius in nautical miles, 5-500, default 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this is a read-only, idempotent, non-destructive, open-world query, so the description doesn't need to re-state safety. It adds genuinely useful context beyond them: the NOAA/NWS Aviation Weather Center source, US-centric coverage, the sparsity and individuality of reports, and a per-call credit cost.

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?

Front-loaded with what the tool returns, then the differentiating claim, then source/coverage/limitation/cost in descending priority. Slightly long, but nearly every clause (coverage, sparsity, cost, not-for-flight-planning) carries information the agent would otherwise have to discover empirically.

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?

No output schema exists, yet the description adequately enumerates the returned fields including the severity tally. Combined with annotations and a fully documented schema, an agent has enough to call it correctly; only the sibling-routing detail and pagination behavior are left implicit.

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%: icao, limit, age_hours and distance_nm all carry types, ranges and defaults in the schema. The description adds nothing about parameter behavior (e.g. how radius interacts with sparsity, or default lookback), so the baseline 3 applies.

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?

States a specific resource (PIREPs), a specific spatial scope (within a distance of an airport), and the exact contents returned (turbulence/icing intensity, altitude, aircraft type, time, plus severity tally). The sentence 'PIREPs are the only first-hand reports of turbulence actually encountered' distinguishes it from forecast/model-based siblings such as metar_latest, taf_forecast and weather.

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 a clear use case ('is it bumpy around Denver right now') and an explicit exclusion ('not for flight planning'), plus a coverage caveat ('mainly the United States', 'reports are sparse'). It stops short of naming the alternative tools (METAR/TAF/weather) an agent should pick for flight planning or non-US coverage, so routing is implied rather than explicit.

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.

Resources