Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

random_airplanes_detailed_info

Returns random aircraft records with model, registration, age, engine details, and delivery/first flight dates. Use it to sample reference data when you don't need a specific registration.

Instructions

Return a random sample of individual airplanes from the reference catalog. Each record has model name and code, series, production line, registration number, owner, age, engine type and count, delivery date and first flight date. Records are drawn from a random offset, so repeated calls return different aircraft. Sampling only: there is no lookup by registration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
number_of_airplanesYesNumber of random airplanes to sample, from 1 to 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedInput schema / properties / number_of_airplanes / description
      Previous value: -"Number of random airplanes to return."New value: +"Number of random airplanes to sample, from 1 to 100."
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / number_of_airplanes / maximum
      Added value: +100
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / number_of_airplanes / description
      Added value: +"Number of random airplanes to return."
    • addedInput schema / properties / number_of_airplanes / exclusiveMinimum
      Added value: +0
    • changedInput schema / title
      Previous value: -"random_airplanes_detailed_infoArguments"New value: +"random_airplanes_detailed_info_toolArguments"
    • changedOutput schema / title
      Previous value: -"random_airplanes_detailed_infoOutput"New value: +"random_airplanes_detailed_info_toolOutput"
  4. First observed

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 behavioral disclosure burden. It transparently explains the random offset mechanism, that repeated calls return different aircraft, and that lookup by registration is not supported. This goes beyond the input schema and gives an agent realistic expectations.

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?

The description is three focused sentences: it states the operation, lists the record contents, and then clarifies sampling behavior and a key limitation. It is front-loaded with the core action and contains no 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 one-parameter tool with an output schema, the description provides all essential context: what is returned, how randomness works, and what the tool cannot do. Nothing critical 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?

The schema has 100% coverage for the single parameter, including range constraints (1 to 100). The description adds only the generic notion of sampling, which is already implied by the tool name and schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Return a random sample of individual airplanes from the reference catalog.' It clearly distinguishes the tool from sibling random_aircraft_type by emphasizing individual airplane records and listing concrete fields, making the tool's purpose unambiguous.

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 explicitly states 'Sampling only: there is no lookup by registration,' which tells an agent when not to use the tool. It does not name sibling alternatives directly, but the sampling-only caveat provides clear usage boundaries.

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