Skip to main content
Glama

Fare Facts

Explain US airline ticket tax and fee codes (free)

explain_tax_codes
Read-onlyIdempotent

US airline ticket taxes and fees: explain two-character tax codes from a ticket receipt (for example US, ZP, AY, XF, YC, XY, XA), with each amount, its effective date and its source (detail 'full' adds every note). Codes not in the verified list are reported as such, never guessed. Fare basis codes are not covered. Free: every Fare Facts tool and answer is free, with no account. Names, confirmation codes (record locators), ticket numbers and frequent flyer numbers are not needed or used; the input is only the codes or numbers in the input schema. The input is the codes alone, for example ["US","ZP","AY","XF"].

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": {
      "codes": "<codes>"
    },
    "name": "explain_tax_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYes1 to 20 two-character tax codes from the ticket's tax box.
detailNoOptional. "brief" (default) gives the main facts; "full" adds every note we have.brief

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 cover the safety profile (readOnly, idempotent, closed-world), and the description adds genuinely useful behavior: unverified codes are reported as unknown rather than guessed, and no PII is required or used. It does not describe response structure or any limits on repeated calls, so it is solid but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and readable, but redundant: 'Free' repeats the title, and the input-only-codes point is made three times ('not needed or used', 'only the codes or numbers in the input schema', 'the codes alone'). Trimming those would sharpen it without losing content.

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 two-parameter lookup tool with no output schema and full annotation coverage, the description supplies everything an agent needs: what it returns, edge-case behavior for unknown codes, an out-of-scope exclusion, and input hygiene constraints.

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%, so the baseline is 3. The description reinforces meaning with concrete code examples and an explicit constraint that only codes should be supplied (no names, record locators, ticket or frequent flyer numbers), which guides how the agent fills the array beyond the schema's pattern/maxItems.

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 (explain) and resource (two-character US airline ticket tax/fee codes) and previews the return content: each amount, effective date, and source. It also carves out what it does NOT cover ('Fare basis codes are not covered'), which distinguishes it from the sibling explain_fare_basis without the agent needing to open either schema.

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?

Clear applicability context: codes come from the ticket's tax box, 1-20 codes, examples given, and the exclusion of fare basis codes signals when to pick a different tool. It stops short of naming the alternative tool explicitly, so the agent must infer the routing rather than being told.

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