Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

airline_lookup

Read-onlyIdempotent

Search airlines by name, IATA/ICAO code, AWB prefix, or country. Returns carrier name, codes, callsign, and verification fields.

Instructions

Search 6,357 airlines by name, IATA code, ICAO code, AWB prefix, or country. AWB prefixes are the first 3 digits of an air waybill number and identify the issuing carrier (e.g. 176 = Emirates).

Provide ONE parameter: query is a ranked fuzzy search across names and codes; iata / icao / prefix / country are exact filters.

Behavior: read-only; fuzzy query hits report their match quality through the envelope's confidence (basis match_quality, score 0-1) with a FUZZY_BEST_MATCH advisory naming the matched field; a query with no hits returns count 0 with a NO_MATCH advisory rather than an error. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits.

Returns: count and results[] — per airline: airline_name, iata_code, icao_code, awb_prefix[], callsign, country, has_cargo, aliases and per-record verification fields — under result, plus confidence, _source and citation (the FreightUtils v1 response envelope).

Limitations: this dataset's provenance is pending independent verification (the envelope's provenance_status says so) — confirm operationally critical codes with IATA/ICAO or the carrier.

Related: airport_lookup (searches AIRPORTS, not carriers), validate (checks an AWB number's check digit and names its airline from this dataset).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iataNoExact IATA code — 2 alphanumeric characters. Examples: "EK", "U2".
icaoNoExact ICAO code — 3 letters. Examples: "UAE", "BAW".
queryNoRanked fuzzy search across name, codes, prefix and country (min 2 chars). Example: "emirates".
prefixNoExact AWB prefix — the first 3 digits of an air waybill. Example: "176".
countryNoFilter by country name (min 2 chars). Example: "Netherlands".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
resultYes
_sourceYes
citationYes
validityNo
warningsNo
confidenceYes
blocking_errorsNo
envelope_versionYes
normalized_inputNo
Behavior5/5

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

Annotations already declare readOnlyHint=true, but description adds substantial detail: read-only behavior, fuzzy match quality, confidence, advisories, rate limiting, error handling, return structure, and data provenance limitations. No contradiction.

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 detailed and well-structured, but slightly long. Every sentence is informative, but could be tightened without losing clarity. It front-loads the purpose and then expands.

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?

Given the tool has 5 parameters, output schema, and annotations, the description covers all necessary aspects: behavior, parameter usage, rate limits, error handling, return structure, limitations, and related tools. It is fully complete.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds value by explaining that query is a ranked fuzzy search while iata/icao/prefix/country are exact filters, and provides examples. It also mentions AWB prefix meaning.

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 clearly states 'Search 6,357 airlines by name, IATA code, ICAO code, AWB prefix, or country.' It specifies the resource (airlines) and action (search/lookup). It also distinguishes from siblings like airport_lookup and validate.

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

Usage Guidelines5/5

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

Explicitly says 'Provide ONE parameter: query is a ranked fuzzy search...' and contrasts exact filters. Mentions behavior for no hits and rate limit handling. Also relates to sibling tools in the last paragraph, providing clear when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SoapyRED/freightutils-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server