Skip to main content
Glama

Starfile

Who owns this aircraft?

aircraft_owner
Read-onlyIdempotent

Look up a U.S. civil aircraft in the FAA registry by tail number (N-number) or Mode S hex code: make, model, year, registration status and dates, and the registrant when it is an organisation (company, LLC, government). Aircraft registered to private individuals are confirmed as such without the person’s name.

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

Input Schema

NameRequiredDescriptionDefault
mode_sNoMode S transponder code as 6 hex characters, e.g. A1B2C3.
n_numberNoTail number, e.g. N12345 or N123AB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior: registrant identity is only returned for organizations, while private individuals are deliberately anonymized. It does not say what happens when the aircraft is not found or when both/neither identifier is supplied (0 required params).

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?

Purpose, identifiers, and returned fields are front-loaded in one dense sentence, with the privacy caveat following. Every clause carries information, though the opening sentence is long enough that splitting the identifier list out would improve scannability.

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?

With no output schema, the description must describe return values and largely does — field list plus the registrant caveat. The main gap is failure behavior (unknown N-number, malformed hex) and the fact that at least one of the two optional parameters must be supplied.

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% and both parameters carry their own format examples, so the schema does the heavy lifting. The description explains that the registrant caveat is tied to lookup outcome rather than adding identifier syntax or semantics beyond the schema; baseline 3 applies.

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 names a specific verb ('look up'), a specific resource ('U.S. civil aircraft in the FAA registry'), and the two lookup keys (N-number, Mode S hex). It then enumerates the returned fields (make, model, year, registration status and dates, registrant), so an agent knows exactly what this tool yields without opening a 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?

It clearly establishes the input mode — either a tail number or a Mode S hex code — which is the key decision an agent must make before calling. It gives no explicit 'do not use for X' guidance or coverage caveat (e.g. non-U.S. or non-civil aircraft), but the scope is narrow and self-evident.

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