Skip to main content
Glama

Add GD&T Callout

add_gdt_callout

Place a GD&T feature control frame on a drawing page to declare tolerances, then let inspection_plan and fai_report read it back as a ballooned characteristic.

Instructions

Place a GD&T feature control frame on a drawing page, so the tolerance is declared on the print: it renders as a compartmented symbol and inspection_plan / fai_report read it back as a ballooned characteristic.

control: ASME Y14.5 characteristic, as gdt_check accepts: flatness, straightness, circularity, cylindricity, profile_line, profile_surface, perpendicularity, parallelism, angularity, position, concentricity, runout, total_runout. zone: tolerance zone mm (Ø-prefixed for position, concentricity, circularity, cylindricity). datums: ordered datum reference frame, e.g. ["A", "B", "C"]. With datums the plan routes it to CMM; datum-free form controls go to the surface plate. feature: optional enumerated feature id (drawing_gate enumerated_features). mmc_bonus: material-condition bonus tolerance, mm. modifier: free text in the tolerance compartment (e.g. "Ⓜ"). x / y: page position mm (origin bottom-left, +Y up).

Returns {handle, name, control, zone, datums, text}.

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>",
      "control": "<control>",
      "zone": "<zone>"
    },
    "name": "add_gdt_callout"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNoFcf
pageYes
viewNo
zoneYes
datumsNo
controlYes
featureNo
modifierNo
mmc_bonusNo
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/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description goes well beyond by explaining the rendered output form, which downstream tools consume it, and how datums change routing. It does not cover whether the callout can be edited/removed later or whether the page must already exist.

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 action and its effect, then a disciplined per-parameter block where every line adds information. Slightly parameter-list heavy but no filler sentences.

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?

For a 12-parameter drawing-mutation tool with no output schema, the description supplies behavior, downstream consumers, and an inline return shape. Only the drawing-page/name/view parameters are left unexplained, which is a modest but real gap.

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?

With only 8% schema description coverage the description carries the load, and it does: enumerates the control vocabulary, explains the Ø prefix rule for zone, specifies the ordered DRF format with an example, and defines the x/y coordinate origin. Gaps remain for page, name (default 'Fcf'), and view, which are undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Place a GD&T feature control frame on a drawing page' — and adds what it becomes downstream (a compartmented symbol read back by inspection_plan/fai_report as a ballooned characteristic). That clearly separates it from add_annotation/add_dimension, though it never names those siblings explicitly.

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?

Gives real conditional context: 'With datums the plan routes it to CMM; datum-free form controls go to the surface plate,' and ties the control vocabulary to what gdt_check accepts. It lacks an explicit when-not-this / use-sibling-instead statement, so it stops short of a 5.

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