Skip to main content
Glama

Draft

draft

Applies a mold-release angle to selected faces of a base feature for moldability, with configurable angle, neutral plane, and direction reversal.

Instructions

Apply a draft angle to faces (for moldability).

base: feature handle. faces: list of {handle, face: tag|'FaceN'}. angle_deg: draft angle (positive degrees). neutral_plane: {handle, face: tag|'FaceN'} for the plane along which the angle is measured (typically the parting plane). reversed: flip the direction of the draft.

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": {
      "base": "<base>",
      "faces": "<faces>"
    },
    "name": "draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
nameNoDraft
facesYes
reversedNo
angle_degNo
workspaceNoRun this call in this named workspace
neutral_planeNo

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

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds that the operation modifies faces by applying a draft angle and explains the reversed/neutral-plane behavior, but it does not disclose workflow requirements, transaction context, or what is returned.

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?

The description is front-loaded with the core purpose and then gives compact parameter notes. It is appropriately sized for a CAD feature tool and contains no redundant or empty prose.

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

Completeness3/5

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

For a 7-parameter mutation tool with low schema coverage and no output schema, the description covers most parameter meanings but omits important workflow context: what the base handle must reference, whether this must occur inside a transaction, and what the operation returns. It is usable but incomplete for reliable chaining and invocation.

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 only 14%, so the description must compensate, and it does document the key parameters: base as a feature handle, faces as a list of {handle, face}, angle_deg as positive degrees, neutral_plane as the measuring plane, and reversed as direction flipping. Minor gaps remain for 'name' and the workspace parameter, though workspace has its own schema description.

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?

The description states a specific CAD operation: applying a draft angle to faces, with the moldability purpose made explicit. It is clearly a feature-creation tool rather than an analysis sibling, but it does not explicitly distinguish itself from related moldability or DFM check tools.

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 parenthetical '(for moldability)' implies the context in which this tool is used, but there is no explicit when-to-use guidance, no prerequisites such as requiring an existing feature handle, and no comparison to alternatives like moldability_check.

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