Aviation Resources

Search FAA Documents

search_documents

Read-only

Full-text search across the FAA handbooks, advisory circulars and other reference documents in Aviation Resources (for example the Pilot's Handbook of Aeronautical Knowledge, Airplane Flying Handbook, Instrument Flying Handbook, Aviation Weather and the Weight & Balance Handbook). Returns the best-matching documents, each with its best pages and short snippets. Use it to find where a topic is covered, then call get_page to read a page in full or see its figures. Cite pages with their viewerUrl.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	How many documents to return.
`query`	Yes	Search terms, e.g. holding entry or "density altitude". Words must all match (English variants count); use "quotes" for a phrase, or for alternatives, and -word to exclude. Use the words an FAA handbook would use; search for an ACS task's topic, not its code.
`offset`	No	How many documents to skip, for the next page of results (pagination.offset + pagination.limit).
`resourceIds`	No	Only search these documents (IDs from earlier results). Leave out to search every document.
`pagesPerResource`	No	How many of each document's best pages to return.

Output Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	The query as it was run.
`results`	Yes	Matching documents, best first. Empty when nothing matches.
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, closed-world operation. The description adds useful behavioral context: it returns best-matching documents with best pages and snippets, and it tells the agent to follow up with get_page and cite viewerUrl.

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 purpose is front-loaded, the corpus is scoped with useful examples, and the remaining sentences cover return shape and next-step usage. The description is compact and every sentence contributes.

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?

Given that annotations cover safety and the output schema exists, the description provides enough context for an agent to use the tool correctly: what corpus is searched, what results look like, and how to proceed to full-page reading. Nothing essential is missing.

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 all five parameters are already documented in the input schema, including query syntax, pagination, limits, and resource filtering. The description adds no parameter-specific semantics beyond the general search story, so the baseline score of 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 and resource: full-text search across FAA handbooks, advisory circulars, and other Aviation Resources documents, with named examples. It clearly distinguishes this lookup/search role from the follow-up reading role of get_page.

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 gives clear usage context: find where a topic is covered, then call get_page to read a page in full or see figures, and cite viewerUrl. It does not explicitly route between this tool and list_airman_certification_standards, so the alternative-tool guidance is not complete.

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

All Aviation Resources tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?