Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

by SoapyRED

airline_lookup

Search 6,352 airlines by name, IATA/ICAO codes, AWB prefixes, or country to find carrier details and verify cargo capabilities.

Instructions

Search 6,352 airlines by name, IATA/ICAO code, AWB prefix, or country.

Use this tool when you need to:

  • Find an airline's IATA code, ICAO code, or air waybill (AWB) prefix

  • Verify airline cargo capabilities

  • Look up airlines by country

AWB prefixes are 3-digit codes used on air waybills to identify the issuing carrier (e.g., 176 = Emirates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoGeneral search (name, code, prefix, or country — min 2 chars)
iataNoExact IATA code (2 chars, e.g., "EK")
icaoNoExact ICAO code (3 chars, e.g., "UAE")
prefixNoAWB prefix (3 digits, e.g., "176")
countryNoFilter by country name (min 2 chars)
Behavior4/5

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

Discloses data scope (6,352 airlines) and educates on domain concept (AWB prefixes), though lacks technical behaviors like rate limits or exact vs. fuzzy matching details (but no annotations contradict).

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?

Perfectly structured with front-loaded purpose, bulleted use cases, and domain explanation; every sentence adds value without bloat.

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?

Complete for a lookup tool of this complexity; explains return value types (codes, cargo capabilities) despite lacking output schema.

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 has 100% description coverage with examples and constraints, so description correctly does not redundantly explain parameters, meeting baseline.

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?

Specific verb ('Search') + resource ('airlines') and clearly distinguishes from logistics siblings (containers, HS codes, calculators) by focusing on carrier identification data.

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?

Explicit 'Use this tool when you need to:' section with three specific scenarios, though lacks explicit 'when not to use' or alternative suggestions.

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