Skip to main content
Glama

Pad

pad

Extrude a sketch by a specified length in millimeters, with an option to add material symmetrically in both directions.

Instructions

Pad a sketch by length mm. symmetric=True extrudes both directions.

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": {
      "sketch": "<sketch>"
    },
    "name": "pad"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPad
lengthNo
sketchYes
reversedNo
symmetricNo
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

B3/5.0
Behavior3/5

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

Annotations already declare that this is a non-destructive, non-readonly operation. The description adds useful behavioral detail about length units and bidirectional extrusion via symmetric=True, but it does not explain model mutation effects, sketch consumption, or failure conditions.

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?

Two short, front-loaded sentences with no wasted text. The key dimensional behavior and symmetric option are presented immediately.

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

Completeness2/5

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

For a CAD mutation tool with no output schema and very low schema description coverage, the description is too thin. It omits prerequisites, resulting feature behavior, and semantics for most parameters, leaving the agent to infer too much.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must compensate. It clarifies `length` units and `symmetric` direction, but leaves `sketch`, `reversed`, and `name` unexplained, and `sketch` is the sole required parameter.

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: padding a sketch by a given length in millimeters. This distinguishes it reasonably well from siblings like pocket or revolve, though it does not explicitly identify the created feature as a solid boss/extrusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what one parameter does but gives no guidance on when to use pad versus pocket, revolve, or other feature-creation tools. It also omits prerequisites such as needing a valid sketch profile.

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