Skip to main content
Glama

GD&T Check

gdt_check
Read-only

Checks a measured feature against a GD&T tolerance zone, returning margin and pass/fail. Use for position, flatness, and other controls to validate manufacturing compliance.

Instructions

Check a measured feature against a GD&T tolerance zone. control: position | flatness | straightness | circularity | cylindricity | perpendicularity | parallelism | angularity | concentricity | runout | total_runout | profile_line | profile_surface. actual is the measured deviation; for position pass offset={x,y} to use the diametral 2*hypot(x,y). mmc_bonus adds bonus tolerance. Returns {control, zone, effective_zone, actual, margin, pass, datum_refs}.

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

Input Schema

NameRequiredDescriptionDefault
zoneYes
actualNo
offsetNo
controlYes
mmc_bonusNo
workspaceNoRun this call in this named workspace
datum_refsNo

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuine behavioral value by naming the exact return keys ({control, zone, effective_zone, actual, margin, pass, datum_refs}) and explaining that mmc_bonus inflates the effective zone. It does not say what happens when actual is null or how a null actual affects pass/margin, which is the remaining behavioral gap.

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: the core action comes first, then the control vocabulary, then the parameter/return semantics. The long control list is necessary information rather than padding, though the single flat paragraph could be broken into parameter/return segments for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 14% schema coverage, and no output schema, the description does well on the return shape and the two non-obvious parameters, but omits the meaning of zone (total width vs. radial) and datum_refs entirely, both of which materially affect a GD&T evaluation. Contextual completeness for a standards-sensitive calculation is therefore only adequate.

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 14% (just workspace), so the description must carry the load and largely does: it enumerates the legal control values, explains actual as the measured deviation, and defines offset as producing a diametral 2*hypot(x,y) zone and mmc_bonus as added tolerance. It leaves zone and datum_refs undescribed, leaving two of seven parameters under-specified.

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 concrete verb and resource: check a measured feature against a GD&T tolerance zone, with the full list of supported controls enumerated. The purpose is unambiguous, but it does not distinguish itself from adjacent tools such as tolerance_stackup, add_gdt_callout, or fit_check.

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?

Usage is implied by the domain framing — you supply a control, a zone, and a measured deviation — and the offset note tells the agent one specific invocation pattern for position. There is no explicit when-to-use/when-not-to-use guidance, no mention of prerequisites (e.g., that this is a pure evaluation and not a drawing annotation), and no routing away from siblings like tolerance_stackup.

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