Aviation Resources

Get Airman Certification Standard

airman_certification_standards

Read-only

Returns one FAA Airman Certification Standard (ACS) in full: every area of operation, each task with its objective, and every knowledge, risk management and skills element with its sub-elements and ACS codes (e.g. PA.I.A.K1a). Get the ID from list_airman_certification_standards. A whole ACS is large (a Private Pilot ACS is close to 1,000 elements), so pass areaOfOperation, and task if you can, when you only need part of it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "acsId": "<acsId>"
    },
    "name": "airman_certification_standards"
  }
}

Input Schema

Name	Required	Description
`task`	No	Only this task of the area of operation, by its letter, e.g. "A". Needs areaOfOperation.
`acsId`	Yes	The ACS's ID, from list_airman_certification_standards.
`areaOfOperation`	No	Only this area of operation, by its Roman numeral, e.g. "I" or "VII". Leave out for the whole ACS.

Output Schema

Name	Required	Description
`counts`	Yes	How much the result holds.
`filter`	Yes	The areaOfOperation and task the result was narrowed to, or null.
`standard`	Yes
`areasOfOperation`	Yes	In ACS order.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, but the description adds valuable behavioral context: the response can be very large, roughly 1,000 elements for a Private Pilot ACS, and the filters exist to avoid that size. It does not discuss auth or error behavior, but the main operational trait, response size, is well disclosed.

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 front-loaded with the return shape, then the ID source, then the size warning and filtering advice. Each sentence adds operational value with 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?

Given the output schema, annotations, and complete parameter coverage, the description supplies everything an agent needs: what is returned, where the ID comes from, and how to avoid unnecessarily large responses. No material gap remains.

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?

Schema description coverage is 100%, so the schema already documents acsId, areaOfOperation, and task. The description still adds useful semantic guidance by explaining that the ID comes from the sibling list tool and that areaOfOperation/task should be used when only part of a large ACS is needed.

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 resource and action: returning one FAA Airman Certification Standard in full, including areas of operation, tasks, objectives, and K/R/S elements with ACS codes. It clearly distinguishes this from the sibling list_airman_certification_standards by saying the ID comes from that list.

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 tells the agent to get the ID from list_airman_certification_standards, and recommends passing areaOfOperation and task when only part of the ACS is needed. This gives clear usage conditions and an alternative workflow without ambiguity.

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?