Skip to main content
Glama

Tolerance Stackup

tolerance_stackup
Read-only

Stack dimension chains to compute worst-case, RSS, and Monte Carlo tolerance results, or derive a chain from a live solid along an axis. Returns min/max bounds, sigma, and Cpk.

Instructions

Stack a dimension chain. Each chain entry is {name, nominal, plus, minus} with plus/minus the signed upper/lower deviations (plus>=minus; symmetric shorthand {nominal, tol}); add direction:-1 for a subtractive/gap link. method: worstcase | rss | montecarlo (each adds a deeper block). Half-bands are read as 3-sigma; cpk/pct_in_spec use spec_min/spec_max if given, else the worst-case bounds. Returns {nominal, worstcase:{min,max,spread}, rss:{sigma,min_3s,max_3s}, montecarlo:{mean,std,cpk,pct_in_spec,spec}}.

Instead of a hand-built chain, pass a live handle (+ axis, '+z'/'-x'/… or [x,y,z]) and the chain is derived off the solid: planar step faces perpendicular to the axis become consecutive station-to-station links (the stack a height gauge reads off a stepped part). Per-link tolerance: default_tol (± mm), else the ISO 2768-1 general class ('f'|'m'|'c'|'v', default 'm' — the drawing-note default for untoleranced dimensions). The result then echoes the derived chain (+ axis, n_step_faces).

seed fixes the montecarlo draw (12345 default) so the same chain returns the same cpk/pct_in_spec run to run — that determinism is a contract, so change it only to check a result is not an artefact of one draw.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tolerance_stackup"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNo+z
seedNo
chainNo
handleNo
methodNoworstcase
generalNom
samplesNo
spec_maxNo
spec_minNo
workspaceNoRun this call in this named workspace
default_tolNo

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

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

Annotations already establish this as a read-only, non-open-world computation. The description adds substantial behavioral detail beyond annotations: method-dependent output blocks, half-band interpretation as 3-sigma, spec fallback behavior, deterministic montecarlo seeding as a contract, and the echo of the derived chain with axis and n_step_faces.

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?

The definition is dense but largely front-loaded and free of filler. Every major sentence contributes to invocation or interpretation, though the phrase 'each adds a deeper block' is slightly vague and the description could be easier to scan if the chain versus handle modes were separated more crisply.

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 complex, multi-parameter analysis tool with no output schema, the description is unusually complete: it describes the return object structure, deterministic seeding, and derived-chain behavior. The main remaining gap is that it does not explicitly state that the caller should supply either chain or handle, nor does it explain the samples parameter.

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 9%, so the description must carry most parameter meaning. It does this well for chain entry structure, signed deviations, direction, method options, handle/axis derivation, default_tol, general class, seed, and spec bounds. It does not explain the samples parameter, leaving one meaningful input partially undocumented.

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?

The description opens with a specific verb and resource: 'Stack a dimension chain.' It further clarifies the two input modes (hand-built chain or live handle) and the supported methods, so the tool's purpose is clear. It does not explicitly differentiate itself from nearby tolerance-related siblings such as tolerance_cost_check or suggest_loosening, which keeps it from a 5.

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?

The description gives clear contextual guidance for choosing between a hand-built chain and a live handle-derived chain, and it explains when to use default_tol versus the ISO 2768-1 general class. It does not name alternative tools or state when not to use this tool, so it falls short of explicit when/when-not/alternatives guidance.

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