Govparse Government Data Gateway

faa_deregistrations_search

Which aircraft were just deregistered (sold, exported, scrapped, or repossessed)? Search FAA aircraft deregistrations (cancel date >= 2022) by last registrant/owner, N-number, mailing state, status, or cancel date (since/before) — the asset-disposal / ownership-exit event for auctioneers, dealers, and asset-based lenders. Returns the aircraft, its last entity-resolved registrant, and the cancel date. FAA public-domain records. [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	cancel_date \| last_action_date :asc\|:desc. Default cancel_date:desc.
`limit`	No	Max rows (default 25, cap 100).
`since`	No	Cancel date on/after this date (YYYY-MM-DD).
`state`	No	Mailing state code(s), CSV.
`before`	No	Cancel date on/before this date (YYYY-MM-DD).
`offset`	No	Rows to skip.
`status`	No	Status code(s), CSV.
`n_number`	No	N-number(s), CSV (leading N optional).
`entity_id`	No	Resolved registrant entity UUID.
`registrant`	No	Last registrant/owner name — suffix/punctuation-insensitive.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJul 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It discloses data source, cost, cancel date constraint (>=2022), and what is returned. It does not cover rate limits or auth but is fairly transparent for a search tool.

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?

The description is front-loaded with a question and efficiently covers purpose, use case, returns, and cost. It is slightly verbose but each sentence earns its place.

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?

Given no output schema, the description adequately describes what is returned, search criteria, and source. It lacks pagination behavior details but is mostly complete for a search tool with 10 optional parameters.

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% with detailed parameter descriptions. The description adds no new semantic information beyond listing some search criteria, so baseline 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 clearly states the tool searches FAA aircraft deregistrations with a specific verb and resource. It distinguishes from siblings like faa_aircraft_search by focusing on deregistrations (ownership-exit events) and lists key search criteria.

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?

The description provides clear context for use, targeting auctioneers, dealers, and asset-based lenders. It implies the tool is for ownership-exit events but does not explicitly name alternatives or state when not to use it.

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

All Govparse Government Data Gateway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct domain and specific action (e.g., FDA approvals vs clearances vs recalls; firmstanding business360 dossier vs search vs screen). Even overlapping concepts like 'business360' vs 'business360_lookup' are distinguished by input (UUID vs name+state). No two tools appear to do the same thing.

Naming Consistency5/5

All tools use a consistent lowercase snake_case pattern with domain prefix (e.g., fda_*, firmstanding_*, fmcsa_*, govcon_*). Action words (search, lookup, screen, feed, stats) follow predictable usage. The naming is uniform and easy to parse.

Tool Count4/5

38 tools is on the higher end but appropriate for a comprehensive government data gateway spanning multiple agencies and datasets. Each domain has a reasonable number of tools (e.g., FMCSA: 7, OFLC: 6). Could potentially be trimmed slightly, but overall well-scoped for the stated purpose.

Completeness5/5

The tool surface covers the major government data sources comprehensively: FDA (approvals, clearances, recalls), FMCSA (carrier census, safety, insurance, etc.), FSIS, DOJ/OFLC, OSHA/EPA/DOL enforcement, SEC insider filings, clinical trials, VA facilities/opportunities/vendors, and federal contracting. No obvious gaps for the stated gateway purpose.

Resources

Need Help?