Skip to main content
Glama

FAI Report

fai_report
Destructive

Generate an AS9102 Form 3 first-article inspection report from a drawing page, compute pass/fail status for ballooned characteristics against limits, and export CSV, SVG, or PDF.

Instructions

First-article inspection report for a drawing page, shaped like AS9102 Rev B Form 3: one row per ballooned characteristic with the Form 3 fields, limits, suggested method, and computed status.

results: balloon number -> measured value; rows are accepted/rejected against limits. For position pass {"x":.., "y":..} (deviation 2·√(x²+y²), as gdt_check). Omit for a BLANK form: every row 'not_evaluated', never a pass. path: optionally write .csv (data), .svg or .pdf (printable table). part / rev: identity stamped in; default page part name / title-block rev. reference: AS9102 field 6 (Reference Location); defaults to each characteristic's view.

NOT a certified AS9102 submission (every artifact says so).

Returns {ok, columns, rows, summary, disclaimer, part, rev, plan_ok, unmeasurable, path?, size?, format?}; ok=False means a characteristic measured out of limits.

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": {
      "page": "<page>"
    },
    "name": "fai_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
revNo
pageYes
partNo
pathNo
ratioNo
resultsNo
referenceNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=false, but the description adds material context they don't carry: a self-declared non-certification disclaimer stamped on every artifact, blank-form semantics, the fact that ok=False encodes out-of-limit measurements, and the side effect of writing a file when `path` is set. It stops short of stating whether an existing CSV/SVG/PDF at `path` is overwritten, which matters given the destructive hint.

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?

It is front-loaded with the one-sentence purpose, then uses a per-parameter block, then the return shape and the out-of-limits rule — logical and skimmable. The density is justified by 8 parameters and no output schema, though the terse keyword style ('part / rev:', 'reference:') is slightly harder to parse than plain sentences would be.

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 no output schema, the description correctly enumerates the return object ({ok, columns, rows, summary, disclaimer, part, rev, plan_ok, unmeasurable, path?, size?, format?}) and explains the one field whose meaning is non-obvious (ok=False). Combined with the blank-form and disclaimer notes, an agent could call this correctly; only `ratio` and overwrite behavior are unaddressed.

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 only 13%, so the description must carry the load, and it does for most parameters: `results` (balloon number to value, nested {x,y} format with the 2·√(x²+y²) formula), `path` (which extensions write data vs. printable table), `part`/`rev` defaults, and `reference` as AS9102 field 6 with its default. `ratio` (default 10) is never explained anywhere, leaving a real gap in an otherwise compensating description.

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 artifact (AS9102 Rev B Form 3 first-article inspection report for a drawing page) and states exactly what one row means — one per ballooned characteristic with fields, limits, method, and computed status. That is distinguishable from siblings like inspection_plan, balloon_drawing, or gdt_check without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one clear usage branch (omit `results` for a blank form where every row is 'not_evaluated') and repeats the position-deviation convention 'as gdt_check' so the two tools agree. However, it never says when to reach for this tool versus `inspection_plan`, `balloon_drawing`, or `export_drawing`, so the routing decision is left to inference.

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

Deploy Server

Other Tools