Skip to main content
Glama

extrude_mesh

Extrude selected mesh geometry in object mode, adding depth or offset to create new surfaces. Specify a name and optional offset to extend 3D models directly.

Instructions

Extrude selected mesh geometry (object-mode helper).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and mostly fails it: it does not say whether geometry is modified in place, whether existing faces are duplicated or replaced, whether the operation is undoable, or what permissions/context are required. The 'object-mode helper' note is the single behavioral disclosure and is too terse to act on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no filler. But its brevity comes from omission rather than efficiency: the parenthetical is ambiguous and the sentence does too little work for a mutation tool.

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?

Although an output schema exists (so return values need not be explained), the definition is a write-style mesh operation with zero annotations and zero parameter documentation. For that complexity level, the description leaves the agent without enough to invoke it confidently, especially regarding the required 'name' argument.

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 0%, so the description must compensate for both parameters and does not. 'name' is never explained (and appears to conflict with 'selected'), and 'offset' — though loosely implied by the concept of extrusion — is never described in terms of units, direction, or what a null default means.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pair 'Extrude ... mesh geometry' is specific enough that an agent knows the general operation. However, the qualifier 'selected mesh geometry' conflicts with the fact that the tool takes a required 'name' argument, leaving it unclear whether the tool operates on the current selection or on a named object; and nothing distinguishes it from siblings like edit_mesh or bevel_mesh beyond the verb.

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?

There is no statement of when to use this tool rather than bevel_mesh, subdivide_mesh, or edit_mesh, and no prerequisites or exclusions. The only contextual hint is the parenthetical '(object-mode helper)', which implies a mode without saying how to satisfy it or what happens if the mode is wrong.

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