A
licenseNot graded
qualityC
maintenanceEnables AI agents to navigate long PDFs by address—sections, pages, tables, figures, notes, and terms—so they can read selectively and cite the PDF page behind each answer.
10
MIT
Aviation Resources
Server Details
Search FAA handbooks and Airman Certification Standards; read and cite pages with figures.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A4.1/5.0
Scored across 3 tools
Disambiguation4/5
The three tools have largely distinct purposes: search_documents locates content, get_page reads a specific page, and list_airman_certification_standards enumerates ACS documents. The only mild overlap is whether search_documents also surfaces ACS material, which could make the listing tool feel partially redundant for discovery.
Naming Consistency5/5
All names use snake_case with a clear verb_noun pattern (get_page, list_airman_certification_standards, search_documents). The convention is predictable and readable despite the long third name.
Tool Count4/5
Three tools is on the thin side but each has a clear role (search, read, enumerate standards), and page navigation is handled via parameters rather than extra tools. Slightly under-scoped for a document-heavy domain, but nothing is gratuitous.
Completeness3/5
Search-and-read is covered, but there is no explicit way to browse the document catalog, get document metadata, or retrieve the actual ACS task/standard text beyond a list with counts. An agent asked to teach to a specific ACS task may hit a dead end unless get_page happens to accept ACS page references.
Available Tools
3 toolsget_pageGet Document PageARead-onlyInspect
Returns one page of an FAA document from Aviation Resources: an image of the whole page plus the full text of the passages on it. Use it after search_documents to read a page in full or to see figures, charts and tables, or to read on with nextPageNumber / previousPageNumber. Cite the page with its viewerUrl.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pageNumber | Yes | 1-based page number in the PDF, as search_documents returns it (not the number printed on the page). | |
| resourceId | Yes | The document's ID, from search_documents. | |
| includeImage | No | Set false to get only the text, for example when reading through several pages. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| image | Yes | Describes the image content block (the whole page), or null when there is none. |
| indexed | Yes | False when the document has no text index yet; passages is then empty. |
| passages | Yes | Every indexed passage that covers this page, in document order. |
| resource | Yes | |
| viewerUrl | Yes | Opens this page in the Aviation Resources web app. Give this to the user as the source link. |
| pageNumber | Yes | |
| nextPageNumber | Yes | The page after, or null on the last page. |
| previousPageNumber | Yes | The page before, or null on the first page. |
| imageUnavailableReason | Yes | Why image is null when an image was asked for. |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds useful behavioral context: it returns both an image and text, supports page-to-page navigation fields, and tells the caller to cite viewerUrl. It does not cover permission or rate-limit behavior, but that is less critical for a read-only paging tool with an output schema.
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 compact and front-loaded: the first sentence states what is returned, and the remaining clauses cover usage, navigation, and citation. Every sentence contributes directly to correct invocation.
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 the rich schema, existing output schema, and read-only annotations, the description supplies the missing context an agent needs: when to call it, what content it returns, how to page through results, and how to cite the page. Nothing essential is omitted.
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 input schema already documents resourceId, pageNumber, and includeImage thoroughly. The description does not add parameter-level meaning beyond the schema; its mention of nextPageNumber/previousPageNumber appears to refer to output navigation fields rather than input parameters.
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 uses a specific verb and resource: it returns one page of an FAA document from Aviation Resources, including the page image and full text. It also distinguishes the tool from search_documents by positioning it as the follow-up read step after searching.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use this tool after search_documents to read a page in full, inspect figures/charts/tables, or continue reading with nextPageNumber/previousPageNumber. That gives clear when-to-use guidance and names the sibling tool that precedes it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_airman_certification_standardsList Airman Certification StandardsARead-onlyInspect
Lists every FAA Airman Certification Standard (ACS) in Aviation Resources, such as Private Pilot - Airplane or Instrument Rating - Airplane, with its ID, whether it is ready for use, and how many areas of operation and tasks it has. Use this first to find the ACS a lesson is for.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| standards | Yes |
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and scope profile is covered. The description adds that each entry carries an ID, a readiness flag, and area-of-operation/task counts, which is useful but largely overlaps the existing output schema. No pagination or ordering behavior is mentioned.
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?
Two tight sentences, front-loaded with the core action and followed by the usage cue. Minimal waste, though the enumeration of returned fields is somewhat redundant given the output schema.
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 an output schema present, the description need not spell out return structure, and the annotation set covers safety. What is included gives an agent enough to know when to call it and roughly what comes back; only ordering/pagination details are absent, which is minor for a zero-parameter listing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a full, unfiltered listing, which is consistent with an empty input schema.
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?
States a specific verb and resource ('Lists every FAA Airman Certification Standard') and gives concrete domain examples (Private Pilot - Airplane, Instrument Rating - Airplane) so the agent knows exactly what population is returned. This clearly separates it from generic siblings like get_page and search_documents.
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?
'Use this first to find the ACS a lesson is for' gives a clear sequencing cue and a downstream use case. It stops short of naming an alternative tool or a when-not-to-use condition, 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.
search_documentsSearch FAA DocumentsARead-onlyInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| query | Yes | The query as it was run. |
| results | Yes | Matching documents, best first. Empty when nothing matches. |
| pagination | Yes |
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- First observed
get_page - First observed
list_airman_certification_standards - First observed
search_documents
Related MCP Connectors
Free FAA private-pilot ground school: source-cited answers, lessons and practice questions.
- PAVEOAuthcom.pavecfi
Read-only flight-training records for CFIs, students and schools: syllabus, schedule, FAR/AIM.
FAA written-test prep: practice questions, readiness diagnostic, METAR/TAF, drone airspace
Free no-key search over CASA, FAA, EASA & ICAO aviation regulations. By Deepsky (deepskyai.com).
Related MCP Servers
- AlicenseBqualityCmaintenanceA multi-step academic figure agent harness that enables AI agents to plan, generate, evaluate, and iterate publication-grade figures from sources like PMIDs, preprints, or freeform briefs.1432 PyPI1Apache 2.0
- FlicenseAqualityBmaintenanceProvides read-only retrieval of STM32 datasheet and reference manual content with exact citations, page numbers, register details, and source hashes so Claude can answer questions or generate code from verified evidence.31-
- AlicenseNot gradedqualityBmaintenanceEnables engineers and AI assistants to search source-backed hardware design guidelines, retrieve detailed conditions and limitations, and trace citations to original sources, all through a read-only offline interface.AGPL 3.0
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.