Skip to main content
Glama

Drawing Gate

drawing_gate
Read-only

Verifies whether placed dimensions on a drawing page fully and non-redundantly reconstruct the part, checking degrees of freedom, datum discipline and ballooning; returns ok or violation codes.

Instructions

Manufacturing-completeness gate for a drawing page: do the placed dimensions fully and non-redundantly reconstruct the part? Reads the real solid + placed dimensions and accounts degrees of freedom, process-aware: 'prismatic' needs each hole located X/Y from a datum and the block sized W×H×T; 'turned' needs only Ø + axial length per step. process='auto' infers it.

Datum discipline (a location not measured from a datum face → no_datum) turns on when faces carry role='datum' (annotate_face), or with datums_declared=True. require_ballooned=True also fails unballooned characteristics (not_ballooned; see balloon_drawing), as a release flow does.

Returns {ok, violations, slots_total, slots_covered, process, features, dimensions, enumerated_features, datum_faces, section_recommended ({recommended, reasons, feature_ids}; see add_section_view), ballooned ({ok, total, ballooned, missing})}. Each violation has a code (under = size/location missing; redundant = DOF dimensioned twice; conflict = twice with disagreeing values; extra = pins nothing; no_datum; not_ballooned) and a reason. ok=True means manufacturing-complete.

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": {
      "page": "<page>"
    },
    "name": "drawing_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
processNoauto
workspaceNoRun this call in this named workspace
datums_declaredNo
require_balloonedNo

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

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

Annotations only declare readOnly and closed-world; the description adds substantial behavioral context: it reads the real solid plus placed dimensions, switches dimensional criteria by process type, activates datum discipline only under specific face-role or datums_declared conditions, and returns detailed violation codes (under, redundant, conflict, extra, no_datum, not_ballooned). This is rich disclosure beyond 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?

The description is dense but front-loads the core question and follows with process rules, datum conditions, and return structure. Every section carries information, though the final return-shape sentence is long and could be split for easier scanning.

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?

With no output schema, the description fully explains the return object fields, the meaning of ok=True, and each violation code. For a complex validation tool, this gives an agent enough to interpret results and act correctly without further documentation.

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 low at 20%, so the description carries most parameter meaning. It explains process values ('prismatic', 'turned', 'auto'), the effect of datums_declared and require_ballooned, and the page context implicitly. It does not elaborate on the workspace parameter, but overall compensates well for the coverage 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+resource: a manufacturing-completeness gate for a drawing page that checks whether placed dimensions fully and non-redundantly reconstruct the part. This clearly distinguishes it from siblings like drawing_legibility or balloon_drawing, so an agent can route on purpose alone.

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?

Provides clear context for when the gate applies: process-aware rules for 'prismatic' vs 'turned', automatic inference with process='auto', and conditional datum discipline or ballooning checks. Names related siblings (annotate_face, balloon_drawing, add_section_view) but does not explicitly exclude alternatives or state when-not-to-use.

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