Skip to main content
Glama

get_airport

Read-onlyIdempotent

Get an airport guide, operating restriction notes and its website. This is not an operational suitability decision.

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": {
      "slug": "<slug>"
    },
    "name": "get_airport"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoRequested content language. Missing translations fall back to English; field_languages records the actual language.en
slugYesExact slug returned by search, not a guessed display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuine value beyond them by naming the returned content (guide, restriction notes, website) and warning that it must not be used for operational suitability judgments.

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 short sentences, the primary content description front-loaded and the caveat last. Nothing is padded or redundant.

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 steps in to name the returned artifacts, and annotations cover the safety profile while the schema fully documents both parameters. An agent has enough to call it correctly; only return structure details (fields, formatting) remain unstated.

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 both parameters carry rich schema descriptions (slug must be the exact value from search, not a guessed name; lang has documented fallback behavior). The description adds nothing about parameters, 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 ('Get') and enumerates the resource contents: airport guide, operating restriction notes, and website. This clearly separates it from search_airports, though it never names that sibling explicitly, so an agent must infer the get-vs-search distinction.

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?

The closing sentence 'This is not an operational suitability decision' sets a negative boundary on use, which is useful scoping. However, it gives no positive when-to-use guidance and never points to an alternative tool for operational decisions.

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