Skip to main content
Glama

Check Airtight Path

check_airtight_path
Read-only

Verify an enclosed-flow part has one continuous void from inlet to outlet, detecting blocked, leaky, or pinched flow paths by capping both ports and analyzing negative space.

Instructions

Functional check for an enclosed-flow part (a vacuum adapter, manifold, duct): is there a single connected void joining the inlet to the outlet, bounded by solid everywhere else? This catches what check_shape cannot — a watertight solid can still have a blocked flow path or a hidden leak. Inspection only: measures, returns no handle, mutates nothing.

handle: the part to inspect. inlet / outlet: a face reference naming each port OPENING (the rim face around the hole) — an f_* tag, 'FaceN', int index, or a role/name declared with annotate_face (e.g. "inlet"). Both ports are sealed with cap solids and the negative-space void is analysed. min_aperture_mm2: optional minimum acceptable bottleneck cross-section; a connected-but-pinched path (a near-zero 'almond slit') then fails. pad_mm: optional bounding-box margin (default max(2.0, 0.05*diagonal)).

Returns a dict (lengths mm, areas mm², volumes mm³): ok (bool) connected AND not leaky AND aperture >= threshold status (str) 'airtight' | 'bottleneck' | 'blocked' | 'leaky' connected (bool) one void joins inlet and outlet leaky (bool) with both ports capped the cavity still reaches ambient, so an unintended opening exists min_aperture_mm2 (float|null) narrowest section of the flow void bottleneck_point ([x,y,z]|null) a point on the narrowest section plane flow_void_volume_mm3 (float|null) volume of the connecting void void_components (int) number of void solids (ambient + enclosed) inlet / outlet (str) the resolved 'FaceN' references pad_mm (float) the margin used

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>",
      "inlet": "<inlet>",
      "outlet": "<outlet>"
    },
    "name": "check_airtight_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
inletYes
handleYes
outletYes
pad_mmNo
workspaceNoRun this call in this named workspace
min_aperture_mm2No

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds substantive mechanics: both ports are sealed with cap solids, the negative-space void is analysed, 'leaky' means the cavity reaches ambient despite both caps, and a pinched path yields status 'bottleneck'. It also restates non-mutation explicitly, which is consistent with, not contradicted by, the annotations.

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 with purpose before parameter detail, and the return-value block is justified because there is no output schema. Length is largely earned, though the description is long enough that a few lines (port-sealing mechanics repeated in the leaky definition) could be tightened.

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 6-parameter, no-output-schema tool, the description documents semantics, defaults, and the full return dict with units and status enum values. Only the workspace parameter is left unexplained, which is a minor gap against the complexity level.

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 17%, so the description carries the burden and largely delivers: inlet/outlet accepted formats are enumerated (f_* tag, 'FaceN', int index, annotate_face role name) and their meaning as port-rim openings is clarified; min_aperture_mm2 and pad_mm get purpose plus the pad default formula. The 'workspace' parameter is never mentioned, leaving one documentation gap.

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?

States a specific verb and resource ('functional check for an enclosed-flow part ... single connected void joining inlet to outlet') and explicitly distinguishes itself from a named sibling ('catches what check_shape cannot — a watertight solid can still have a blocked flow path'). An agent can tell exactly what this is and what it is not.

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?

Gives clear context for use (enclosed-flow parts: vacuum adapters, manifolds, ducts) and names check_shape as the inadequate alternative. It stops short of stating prerequisites or explicit when-not-to-use conditions, so it sits 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