Document support and integration planning
FAA 8130-3 MCP: Catalog Status
No. tools/list returning extract_easa_form1 does not mean 8130-3 is supported because both are release certificates. Tool discovery is not document support. Mixing those ideas is how FAA tags get stuffed into an EASA schema by accident on the first job.
Check the advertised document type before building an FAA 8130-3 MCP workflow. ChatGPT can still transcribe visible blocks on an attached tag; Doana will not call that transcription a public FAA extraction tool or a job envelope.
Public catalog as of 12 September 2026: extract_easa_form1 only.
Tool discovery is not FAA support
No. After connecting a server, inspect tools/list and the advertised document type. A tool named extract_easa_form1 is not a generic certificate parser. Require an explicit FAA schema and representative validation results before relying on FAA extraction in your application code.
The public catalog does not publish a dedicated FAA 8130-3 extraction operation. Do not send an FAA-only certificate to the EASA tool on the assumption that a similar layout makes it supported. As of 12 September 2026, extract_easa_form1 is the only advertised extraction tool.
ChatGPT transcription is not a Doana tool
ChatGPT can transcribe visible 8130-3 blocks into a table if you attach the file. That is a model reading pixels or text. It does not create a Doana job_id, documentType, or uncertainFields path list from an FAA schema. Doana will not certify that transcript.
Keep unreadable text marked unreadable. Separate transcription from interpretation. Do not copy EASA confidence numbers onto FAA rows. For a supported extraction path, use EASA Form 1 with extract_easa_form1 after OAuth, then review uncertainFields against that source Form 1 PDF.
Classify mixed packets first
Classify each document before selecting a tool. Keep an FAA-only document outside the supported EASA path. Discuss dual-release or ambiguous certificates with Doana using redacted samples rather than assuming all similar layouts are interchangeable extraction targets for extract_easa_form1. documentType unknown is not an 8130-3 parse; it is usually a succeeded job with no Form 1.
If extract_easa_form1 returns documentType unknown, leave the FAA tag in a human queue. Do not invent Block mappings in the agent prompt. The FAA export airworthiness pages remain the reference for the form’s meaning. Scan quality still matters: a blurry 8130-3 is a reading problem, not a reason to force the EASA tool.
Contact before planning FAA extraction
Contact Doana with redacted examples, expected fields, scan quality and who will review output. Agree how part numbers, serials, quantities and remarks would be represented if a tool is later offered. Until then, keep FAA work off production MCP jobs.
You may still prototype OAuth and uploads with an EASA Form 1. Label that prototype clearly so nobody files an FAA-related change ticket against it. Keep ChatGPT 8130-3 tables in a review folder named transcription, never in a column named Doana FAA result.