Skip to main content
Glama

Envelope Check

envelope_check
Read-only

Verify that each named part’s world bounding box stays within its declared assembly envelope, and return axis-level violations when any part exceeds its allowed bounds.

Instructions

Keep-out gate: assert each named part's world bounding box stays inside its declared envelope. envelopes maps a part's link name (or label) to {"min": [x,y,z], "max": [x,y,z]} in the assembly frame. Returns violations [{part, axis, got, allowed}, ...]; empty means everything is within its box.

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": {
      "assembly": "<assembly>",
      "envelopes": "<envelopes>"
    },
    "name": "envelope_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
assemblyYes
envelopesYes
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

A3.9/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 safety is covered. The description meaningfully adds that envelopes are expressed in the assembly frame, that results are violations with part/axis/got/allowed fields, and that an empty return means everything is within its box. It does not describe error behavior for unknown parts or invalid envelope data, but it provides substantial behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly written sentences with no waste. The gate concept is front-loaded, followed by the envelopes input format and then the return semantics, which is a logical structure for an agent to parse.

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 read-only check with a nested input object and no output schema, the description supplies the essential input structure and return format. It omits what the assembly string should contain and does not address failure modes or unknown part keys, so it is strong but not fully complete.

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 coverage is only 33%, so the description carries much of the burden. It fully explains the complex envelopes parameter, including that keys are part link names or labels and values are min/max XYZ arrays in the assembly frame. The required assembly parameter is only indirectly described through 'assembly frame', and workspace semantics come from the schema.

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: assert each named part's world bounding box stays inside its declared envelope, framed as a keep-out gate. This is clear enough to distinguish the general operation, but it does not explicitly differentiate itself from nearby checks such as interference_check, min_clearance, or bounding_box.

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?

The phrase 'keep-out gate' implies the tool is used for envelope compliance validation, but there is no explicit when-to-use or when-not-to-use guidance. It does not name alternative tools or say when an agent should choose this over clearance, interference, or bounding-box inspection tools.

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