open-transfer-times

Get an airport's transfer profile

get_airport_profile

Read-onlyIdempotent

Retrieves transfer allowances and cited facts for an airport, showing whether each is a heuristic estimate or sourced data. Airports without a profile fall back to the standard baseline.

Instructions

Return the transfer allowances used for an airport, whether each is a heuristic estimate or sourced, and the cited facts (with official source links) about transferring there. Airports without a profile use the standard baseline.

Input Schema

Name	Required	Description	Default
`airport`	Yes	IATA airport code, e.g. LHR

Output Schema

Name	Required	Description	Default
`iata`	Yes
`name`	No
`facts`	Yes
`coverage`	Yes
`allowances`	Yes
`has_profile`	Yes
`last_reviewed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context beyond that, disclosing data provenance, official source links, and the standard-baseline fallback for missing profiles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the return contents and followed immediately by the fallback rule. There is no waste or redundancy.

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?

For a single-parameter read-only lookup with annotations and an output schema, the description is complete enough. It covers the returned information and the missing-profile fallback behavior.

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 schema fully documents the single airport parameter as an IATA code with an example. The description does not add syntax or format detail beyond the schema, so baseline 3 is appropriate when schema coverage is 100%.

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 and resource: returns an airport's transfer allowances, including whether each is heuristic or sourced and cited facts with links. The purpose is clear, though it does not explicitly distinguish this lookup from siblings like check_connection or compare_connections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what is returned and notes the baseline fallback for airports without a profile, but gives no explicit guidance on when to use this tool versus alternatives. It leaves usage selection to inference.

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

Deploy Server