Skip to main content
Glama

get_flights

Read-onlyIdempotent

Get current flight information for Keflavík International Airport.

Returns flight number, airline, origin/destination, scheduled and estimated times, and current status (on time, delayed, landed, etc.).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of flights to return.
languageNoResponse language: 'en' for English, 'is' for Icelandic.en
flight_typeNoWhether to return arrivals or departures at Keflavik Airport.arrivals

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and not open-world; the description adds that data is current and enumerates status values. It does not add operational caveats such as refresh frequency or rate limits, so it is adequate but not rich beyond annotations.

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 tight sentences: the first states the resource and location, the second summarizes return values. Nothing is repetitive or padded.

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 simple read-only airport-flight lookup, the definition covers the resource and result scope, while annotations supply safety traits and the output schema covers return structure. No essential calling information is missing.

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?

All three parameters have complete schema descriptions and two enums, so the schema carries parameter meaning. The description does not mention limit, language, or flight_type, adding no semantics beyond the schema.

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 names a specific verb ('Get') and resource ('current flight information') and pins it to Keflavík International Airport. It also lists the returned fields, making it clearly distinguishable from the unrelated sibling tools.

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?

It establishes the context as current flights at a named airport, but it does not state when to prefer this over alternatives or any exclusions. The absence of a flight-specific sibling makes that less costly, but guidance is only implied.

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