Skip to main content
Glama

search_aircraft

Read-onlyIdempotent

Search JetAtlas aircraft specifications and estimated prices/costs. Returns published configurations and citation URLs, not operational approval.

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": "search_aircraft"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoRequested content language. Missing translations fall back to English; field_languages records the actual language.en
limitNoMaximum records per page.
queryNoWords or codes to match, case-insensitive.
offsetNoOffset for the next page.
statusNo
categoryNo
min_seatsNoMinimum typical passenger seats.
manufacturerNoExact slug returned by search, not a guessed display name.
min_range_nmNoMinimum published range in nautical miles.
max_price_usd_mNoMaximum estimated new price, millions of USD. Unknown prices are excluded.

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context beyond them: it discloses what the results actually contain (published configurations plus citation URLs) and explicitly warns that output is not operational approval, which is real behavioral information. It says nothing about pagination, which limit/offset imply.

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?

Two tight sentences with zero filler, and the primary purpose is front-loaded ahead of the scoping caveat. Every sentence earns its place.

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?

There is no output schema, so the description must partly carry return-value meaning, and it does (published configurations, citation URLs). With 10 mostly self-documented parameters and annotations covering the safety profile, the definition is largely complete; it could still say more about pagination or how query combines with the filter fields.

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 80%, so the schema already documents nearly every parameter (lang fallback behavior, limit/offset paging, manufacturer slug, unknown-price exclusion). The description only loosely gestures at 'estimated prices/costs' and 'published configurations', adding little syntax or semantics beyond the schema. Baseline 3 is appropriate.

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 (Search) and resource (JetAtlas aircraft specifications and estimated prices/costs), and the caveat 'returns published configurations and citation URLs, not operational approval' scopes exactly what kind of aircraft data this covers. This lets an agent distinguish it from get_aircraft (single-record fetch) and compare_aircraft 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?

Usage is implied by the verb 'search' plus the filterable schema, but the description names no alternatives and gives no explicit when-to-use/when-not guidance (e.g. when to prefer compare_aircraft or get_aircraft). The boundary note about not being operational approval hints at a constraint but is not routing guidance.

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