Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_taxes

Find aviation taxes in a reference catalog using pagination and optional text search. Filter by tax name or IATA code to retrieve static tax IDs and codes.

Instructions

List aviation taxes from the reference catalog, one page at a time, with optional text search. Each record has tax id, tax name and the associated IATA code, alongside a pagination block carrying limit, offset and total. This is static reference data, not fares or amounts charged on a booking. Requires a paid plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tax records to return per page, from 1 to 100.
offsetNoZero-based offset for pagination. Combine with limit and the total in the response to page through results.
searchNoOptional text matched against tax name and IATA code.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.8.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of tax records to return."New value: +"Maximum number of tax records to return per page, from 1 to 100."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination."New value: +"Zero-based offset for pagination. Combine with limit and the total in the response to page through results."
    • changedInput schema / properties / search / description
      Previous value: -"Optional tax search text."New value: +"Optional text matched against tax name and IATA code."
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / limit / maximum
      Added value: +100
  3. Addedv1.6.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the pagination model, record structure (tax id, tax name, IATA code), the static reference data nature, and the paid plan prerequisite. This goes beyond what the schema provides, though it omits details like rate limits or error behavior.

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?

Every sentence earns its place: the first states the core action, the second describes the response shape, and the third clarifies data type and access requirement. It is concise, front-loaded, and free of filler.

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 straightforward list tool with three optional parameters and an output schema, the description is complete. It explains what is returned, pagination semantics, the nature of the data, and the prerequisite paid plan. No critical missing information is apparent for an agent to invoke it correctly.

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 the baseline is 3. The description does echo the search and pagination parameters conceptually, but it does not add meaningful semantic detail beyond what the input schema already documents for limit, offset, and search.

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 states a specific verb ('List'), resource ('aviation taxes from the reference catalog'), and key behaviors (pagination, optional text search). It also distinguishes the tool from fare/booking charge data by clarifying it is static reference data, which separates it from potentially confusing uses and 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 Guidelines4/5

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

The description provides clear context on when to use the tool: for static reference data, not for fares or amounts charged. It also notes the paid plan requirement. However, it does not explicitly name alternative tools or state when not to use this tool in favor of a sibling, so it falls short of a 5.

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

Deploy Server

Other Tools