Skip to main content
Glama

Inspection Plan

inspection_plan
Read-only

Generates a ballooned inspection characteristic list for a drawing page, including nominal limits and a suggested measurement method per row, and flags features that cannot be inspected as drawn.

Instructions

The ballooned characteristic list for a drawing page as data (every dimension, feature control frame, feature note), with nominal, limits, and a suggested measurement method per row. The method follows the tolerance: the ratio:1 gauge rule (default 10:1) walked down a per-family instrument ladder (bores use pin/bore gauges; datum-referenced GD&T → CMM; datum-free form → surface plate). Resolution is exact; instrument mapping is shop convention, hence fidelity='correlation'.

Returns {ok, characteristics, count, by_method, unmeasurable, retired, next_balloon, fidelity, band_pct, basis}. ok=False means something cannot be inspected as drawn: no_tolerance (untoleranced size) or no_instrument (band finer than any instrument), named in unmeasurable.

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": "inspection_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
ratioNo
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

A3.9/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already covering safety, the description adds real substance: how the method derives from tolerance via the ratio:1 gauge rule and per-family instrument ladder, that resolution is exact while instrument mapping is shop convention (fidelity='correlation'), and explicit failure semantics (ok=False with no_tolerance or no_instrument named in `unmeasurable`). What it does not disclose is pagination/next_balloon continuation behavior, which is one gap short of a 5.

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?

Front-loaded with the core output, then the method-derivation logic, then failure modes and return keys; nearly every clause carries information. The telegraphic arrow notation ('datum-referenced GD&T → CMM') is dense but efficient for a technical agent audience.

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?

No output schema exists, and the description compensates by enumerating the returned keys (ok, characteristics, count, by_method, unmeasurable, retired, next_balloon, fidelity, band_pct, basis) and the meaning of ok=False. The remaining hole is the `page` argument's expected form, which an agent would otherwise have to guess.

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 description coverage is only 33%: only `workspace` is documented in the schema. The description meaningfully explains `ratio` (the 10:1 gauge rule baseline) and implies `page` is a drawing page, but it never specifies the page's expected format (name, index, or handle), leaving the sole required parameter underspecified.

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?

States a specific verb+resource: produces the ballooned characteristic list for a drawing page as structured data, including nominal, limits, and suggested measurement method per row. That vocabulary clearly separates it from sibling tools like balloon_drawing, fai_report, and gdt_check, which serve different stages of the drawing workflow.

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?

The usage context is implied rather than stated: it operates on 'a drawing page' with balloons, but the description never says when to call this instead of balloon_drawing or fai_report, nor what preconditions (balloons already placed, page fitted) must hold before it returns meaningful data.

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