Skip to main content
Glama

extrude

Create a 3D solid from a 2D sketch profile by pulling it linearly. Supports symmetric, one-direction, or two-direction pulls with taper and boolean operations.

Instructions

Extrude a sketch profile to create a solid body. Supports symmetric, one-direction, or two-direction extrusion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sketch_indexNoIndex of the sketch containing the profile (0-based). Uses last sketch if not specified.
profile_indexNoIndex of the profile within the sketch (0-based). Uses first profile (0) if not specified.
distanceYesExtrusion distance in mm.
directionNoExtrusion direction: 'positive', 'negative', or 'symmetric'.positive
operationNoBoolean operation: 'new_body', 'join', 'cut', 'intersect'.new_body
taper_angleNoTaper angle in degrees (0 = no taper).
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions creating a solid body but omits behavioral traits like boolean operations (join/cut/intersect) or taper angle behavior. Does not disclose failure modes or effects of different direction modes.

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?

Single sentence, front-loaded with action, no wasted words. Efficient and clear.

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

Completeness1/5

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

Given tool complexity (6 parameters, boolean operations, taper, multiple directions), description is too sparse. Does not explain two-direction extrusion, operation types, or taper angle. No output schema, yet no hint about return value. Lacks key details for correct use.

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 100%, so schema already describes parameters. Description adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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?

The description clearly states the verb 'extrude' on a 'sketch profile' to create a 'solid body', distinguishing it from sibling tools like revolve or loft. It also mentions supported directions (symmetric, one-direction, two-direction).

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?

No guidance on when to use this tool vs alternatives (e.g., revolve, loft). Does not specify prerequisites or when not to use it. Only states what it does without contextual advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikan-atomoki/text-to-model'

If you have feedback or need assistance with the MCP directory API, please join our Discord server