Skip to main content
Glama

Suggest Loosening

suggest_loosening
Read-only

Recommends tolerance links to loosen one IT grade at a time for cost savings, re-checking Cpk so the stack remains within spec.

Instructions

The loosest tolerance that works: which links can give up tolerance for the biggest cost saving while the stack still passes.

Greedy, one IT grade at a time — every trial loosening is re-verified against tolerance_stackup's seeded Monte-Carlo cpk before it is committed, so nothing it suggests can fail the spec. Candidates are ranked by the tolerance_cost_check curve, so the tightest (most expensive) links get opened first. Loosening preserves each link's MEAN, so the stack's nominal does not move.

Two honest refusals: a chain that does not already meet target_cpk returns ok=False (there is no margin to give away — tighten or re-spec, do not loosen), and an already-loosest chain returns steps=[] with saving=0 rather than inventing a saving. stopped says which: 'no_further_move' | 'max_steps' (re-run on the returned chain to continue) | 'no_margin'.

chain / handle / axis / default_tol / general as in tolerance_cost_check; spec_min/spec_max default to the chain's own worst-case bounds. Returns {ok, steps:[{link, index, from_it, to_it, from_band_mm, to_band_mm, cost_before, cost_after, saving, cpk}], stopped, chain (the loosened scheme), cost_index_before, cost_index_after, saving, saving_pct, cpk_before, cpk_after, target_cpk, spec, note, fidelity, band_pct, basis}.

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

Input Schema

NameRequiredDescriptionDefault
axisNo+z
seedNo
chainNo
handleNo
generalNom
processNocnc
samplesNo
spec_maxNo
spec_minNo
max_stepsNo
workspaceNoRun this call in this named workspace
target_cpkNo
coarsest_itNo
default_tolNo
step_gradesNo

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

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

Beyond the readOnlyHint annotation, the description discloses the greedy one-grade-at-a-time algorithm, seeded Monte-Carlo re-verification, cost-curve ranking, mean preservation, refusal behavior, and stopped reasons. It also explains that suggestions cannot fail spec and lists the returned fields, which is unusually rich behavioral context.

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 description front-loads the core purpose and then packs algorithm, refusal, and return details efficiently. It is dense but largely justified by the tool's complexity and the absence of an output schema, though some references such as 'as in tolerance_cost_check' are terse.

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 tolerance-optimization tool with no output schema, the description covers the algorithm, guarantees, refusal modes, and return structure well enough for an agent to understand behavior. It is not fully complete because many input parameters remain undocumented despite the low schema coverage.

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?

It adds meaning for several key parameters such as target_cpk, spec_min/spec_max defaults, chain, handle, axis, default_tol, and general by referencing tolerance_cost_check. However, with 15 parameters and only 7% schema description coverage, important tuning parameters such as seed, process, samples, coarsest_it, and step_grades are not meaningfully explained.

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 states a specific optimization purpose: find the loosest tolerances that preserve spec while maximizing cost saving, using greedy IT-grade steps. It explicitly distinguishes its role from tolerance_stackup verification and tolerance_cost_check ranking, so an agent can identify the operation without opening siblings.

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?

It gives clear usage context and exclusions: do not loosen when the chain does not already meet target_cpk because there is no margin to give away, and it explains the already-loosest case. It also mentions re-running on the returned chain to continue, but does not explicitly compare itself against every relevant sibling in a when-to-use/when-not-to-use list.

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