Skip to main content
Glama

Verify Feature

verify_feature
Read-only

Compares a feature's actual volume change against the expected signed delta after additive or subtractive operations to catch silent failures like under-cut pockets or misdrilled holes.

Instructions

Compare a feature's actual volume change against an expected signed delta. Run after each subtractive/additive operation to catch silent failures — Pocket on a curved surface that under-cut, Hole that drilled outside the body, Cut whose Tool didn't intersect the Base.

handle: PartDesign feature (Pad/Pocket/Hole/Revolve/etc.) or Part::Cut. expected_delta_mm3: SIGNED expected change. Subtractive → negative, additive → positive. Wrong sign is its own useful error. tolerance: relative tolerance (default 0.05 = 5%). abs_tolerance: absolute mm³ fallback for tiny expected magnitudes (default 0.01). Pass if EITHER tolerance is satisfied.

Returns {passed, message, actual_delta_mm3, expected_delta_mm3, ratio, previous_volume_mm3, current_volume_mm3, handle, name}. Does NOT raise on mismatch — inspect passed to decide whether to abort.

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": {
      "handle": "<handle>",
      "expected_delta_mm3": "<expected_delta_mm3>"
    },
    "name": "verify_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
toleranceNo
workspaceNoRun this call in this named workspace
abs_toleranceNo
expected_delta_mm3Yes

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

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

Beyond the readOnlyHint annotation, it discloses the critical behavioral contract: the tool does NOT raise on mismatch, so the caller must inspect `passed` to decide whether to abort. It also enumerates the full return payload and explains that a wrong sign is itself a diagnostic signal — none of which is available from the annotations or schema.

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?

It is front-loaded with purpose, then usage, then per-parameter notes, then return contract — a clean order. A few phrases (the three-item failure catalogue, "Wrong sign is its own useful error") are illustrative rather than strictly necessary, keeping it just below maximum conciseness.

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

Completeness5/5

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

There is no output schema, but the description enumerates every returned field, so an agent knows exactly what it can inspect. Combined with the parameter notes and the non-raising warning, nothing an agent needs to invoke and interpret this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20%, but the description compensates for nearly all of it: it defines the accepted handle types (PartDesign feature or Part::Cut), the signed convention for expected_delta_mm3 with the subtractive/additive mapping, and the relative-vs-absolute tolerance interplay including the "pass if EITHER is satisfied" rule. Only `workspace` is left to the schema, which already documents it.

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 first sentence states a specific verb and resource: compare a feature's actual volume change against an expected signed delta. It is immediately distinguishable from siblings like check_shape or mass_properties, which report state rather than validating a predicted delta.

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 a clear trigger — "run after each subtractive/additive operation" — and names concrete failure modes it catches (under-cut Pocket, Hole outside the body, non-intersecting Cut). It stops short of naming alternatives or exclusions (e.g., when to use this instead of verify_intent or check_shape), so it lands at 4 rather than 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