Skip to main content
Glama

chamfer_extrude_3d

Extrudes an active single-part planar 2D drawing into an exact Open CASCADE 3D B-Rep solid, with optional STEP or STL export and configurable thickness.

Instructions

Extrude the active single-part planar 2D drawing into an exact Open CASCADE 3D B-Rep solid and optionally save STEP or STL to disk.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chamfer_extrude_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNostep
overwriteNoAllow replacing an existing file at output_path.
output_pathNoOptional path to save the exported .step/.stp or .stl file.
thickness_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this is a constructive/exporting operation (creates a solid, optionally writes a file) and notes the overwrite path behavior via the schema. However it says nothing about failure modes (non-closed or non-planar profile, multiple parts in the drawing), whether the drawing is modified, or what is returned when no output_path is given.

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?

A single dense sentence with the operation, input scope, output artifact, and optional export all front-loaded; no redundant or filler phrasing.

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 geometry-creating tool with no annotations and no output schema, the definition covers what it produces and where files go but omits error conditions, unit semantics for the thickness, and what the call returns when saving is skipped. Adequate to attempt the call, not adequate to predict its behavior.

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

Parameters3/5

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

Schema coverage is 50%: overwrite and output_path are already documented in the schema, and the description only restates the STEP/STL choice for format. Critically, thickness_mm — the parameter that determines the solid geometry — is never explained beyond its default of 5, so the description does not compensate for the coverage gap.

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?

Names a specific verb and resource chain: extrude the active single-part planar 2D drawing into an Open CASCADE 3D B-Rep solid, with optional STEP/STL export. The 'active single-part planar' qualifier signals it operates on current drawing state rather than an imported file, which implicitly separates it from chamfer_import_dxf and chamfer_export_dxf, but no sibling is named explicitly.

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?

Usage is only implied: the phrase 'active single-part planar 2D drawing' hints at the preconditions (a loaded drawing, one part, planar profile), but there is no explicit when-to-use/when-not statement and no stated alternative for producing 2D exports or running CAM. An agent must infer the workflow position.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.