Loading ToolBench
FAA Regulations MCP — US Federal Aviation Regulations (14 CFR, 'FARs'). A thin, FAA-branded, keyless wrapper over the official eCFR API, scoped to the whole of Title 14 (all of it is FAA / aviation).
Two well-named, read-only tools with comprehensive descriptions and proper JSON schemas. Tool names (faa_regulation, faa_search) follow verb_noun convention and clearly signal intent. Descriptions are detailed (300+ chars each) and include use cases, examples, and input flexibility guidance. Input schemas are complete with type declarations and parameter descriptions. However, output schemas are not documented, LLMs cannot predict response structure for downstream planning. Error handling is minimal (no recovery guidance, no categorization). No tool annotations (readOnlyHint present implicitly via Risk field, but not in schema). Missing pagination guidance for faa_search despite accepting a limit parameter.
Get the full text of one Federal Aviation Regulation (FAR) — a US FAA / aviation regulation codified in 14 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does FAR 91.113 say", "what is the FAA regulation for X", "does the FAA require X", "read 14 CFR 107.29", "the FAA right-of-way rule". Forgiving citation input: "91.113", "14 CFR 91.113", "FAR 91.113", "§91.113", even "91.113(b)" (paragraph stripped to the section). Covers 14 CFR part 91 general operating & flight rules, part 121 airline/scheduled operations, part 135 commuter & on-demand, part 107 small unmanned aircraft (drone) rules, part 61 pilot/airman certification, part 43 maintenance, part 145 repair stations, part 25 aircraft airworthiness — the whole of Title 14 (aviation, aircraft, airspace, pilots). Pass a whole part (e.g. "91" or "107") to get that part's section list. Example: faa_regulation({ citation: "91.113" }) -> right-of-way rules; faa_regulation({ citation: "FAR 107.29" }) -> drone operation at night. Keyless.
Keyword search across the Federal Aviation Regulations — US FAA / aviation rules in 14 CFR. Answers "what FAA regulations cover X", "the aviation rule / FAR about X", "find the FAA regulation for X". Great for topics: right-of-way, VFR/IFR flight rules, minimum safe altitudes, drone / small unmanned aircraft operations, remote pilot certification, airline operating requirements, pilot certification and medical, aircraft airworthiness, maintenance and repair stations, airspace, TFRs. Returns matching Federal Aviation Regulations with citation (14 CFR / FAR), heading, excerpt, and source URL. Note: the CFR text uses "unmanned aircraft", not "drone" — search "unmanned aircraft night" for drone-at-night rules. Example: faa_search({ query: "unmanned aircraft night" }); faa_search({ query: "right-of-way rules", limit: 15 }). Keyless.
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting) for faa_regulation and faa_search. Blocks downstream tool chaining and forces LLMs to guess at response format.
No error handling guidance. Errors from eCFR API (503, timeout, malformed citation) are not categorized as retryable/user-fixable/fatal. LLMs receive raw error messages with no recovery path.
faa_search accepts limit parameter (1-20) but no pagination cursor or offset. Large result sets cannot be paginated; LLMs cannot fetch next page of results.
Tool annotations missing from schema. Risk field (READ_ONLY) is metadata outside the MCP schema; readOnlyHint should be declared in inputSchema for spec compliance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2026-07-28+ | v2 |
Transport mechanism unknown. No evidence of HTTP, SSE, or STDIO transport in package.json or index.ts. Cannot assess remote accessibility or protocol compliance.