Skip to main content
Glama

BRAINIAC Tariffs & Trade Reference

Look up a US airport or landing facility

trade-tariff_us-airport-lookup
Read-onlyIdempotent

Look up a US landing facility by FAA location identifier, ICAO id or name from the vendored FAA NASR 28-day APT_BASE data. Price $0.01 USDC. POST /api/v1/trade-tariff/us-airport-lookup. An unpaid call returns the x402 payment terms and does not run.

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": "trade-tariff_us-airport-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
icaoNoicao, string. Optional.
nameNoname, string, length 2 to 100. Optional.
faaIdNofaaId, string. Optional.
limitNolimit, integer, from 1 to 50. Required.
stateNostate, string. Optional.

Output Schema

NameRequiredDescriptionDefault
cycleNocycle. String.
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: a $0.01 USDC price, the POST /api/v1/... endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not execute. That payment/auth disclosure is exactly the kind of behavioral detail annotations cannot carry.

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?

Three short sentences, front-loaded with the lookup purpose before the commercial and transport details. Every sentence carries information, though the raw endpoint path is somewhat redundant for an agent that just calls the tool.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety hints. The description closes the remaining gaps an agent would hit: cost, transport, and the unpaid-call behavior. Nothing material is missing for correct invocation.

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 description coverage is 100%, so all five parameters (icao, name, faaId, state, limit) are already documented with patterns and bounds; the baseline of 3 applies. The description names the identifier parameters but adds no extra meaning for 'state' or 'limit', nor any note on combining filters or which identifier takes precedence.

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?

States a specific verb ('Look up') and resource ('US landing facility') plus the three lookup keys (FAA location identifier, ICAO id, name) and the backing dataset (FAA NASR 28-day APT_BASE). This is clearly distinguishable from siblings like hts-duty-rate-lookup or uk-global-tariff-lookup without opening any schema.

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 lookup keys imply when to use it (you have an airport id or name), but there is no explicit when-to-use/when-not guidance and no named alternative or fallback when an identifier isn't found. The payment sentence is behavioral, not usage guidance, so context 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