Skip to main content
Glama

blender_mesh

Create, duplicate, delete, and modify mesh objects in Blender, including cubes, spheres, cylinders, cones, planes, torus, and monkey primitives, with operations like extrusion, bevel, subdivide, and joining.

Instructions

PORTMANTEAU PATTERN RATIONALE: Consolidates 9 related mesh operations into single interface. Prevents tool explosion while maintaining full primitive creation and object management functionality. Follows FastMCP 2.14.3 best practices.

Create and manipulate mesh objects in Blender with comprehensive primitive support.

Core Operations:

  • create_cube: Generate cube primitive with customizable dimensions

  • create_sphere: Generate sphere primitive with vertex control

  • create_cylinder: Generate cylinder primitive with radius/depth control

  • create_cone: Generate cone primitive with radius/depth control

  • create_plane: Generate plane primitive for ground/floor surfaces

  • create_torus: Generate torus primitive with ring/tube radius control

  • create_monkey: Generate Suzanne (monkey) primitive for testing

  • duplicate_object: Create copies of existing objects with transforms

  • delete_object: Remove objects from scene by name

  • extrude: Extrude mesh region along +Z in edit mode

  • inset: Inset selected faces

  • bevel_modifier: Add bevel modifier to mesh object

  • subdivide: Subdivide mesh edges

  • merge_vertices: Merge by distance (remove doubles)

  • delete_faces: Delete selected faces in edit mode

  • join: Join multiple mesh objects into one

  • separate_loose: Separate loose parts to new objects

  • triangulate: Convert quads to triangles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe mesh operation to perform. Must be one of: "create_cube", "create_sphere", "create_cylinder", "create_cone", "create_plane", "create_torus", "create_monkey", "duplicate_object", "delete_object". - "create_*": Create new primitive objects (require: name, may use: location, scale, radius, depth, vertices) - "duplicate_object": Copy existing object (requires: source_name, name) - "delete_object": Remove object from scene (requires: name)create_cube
nameNoName for the new object or object to delete. Must be unique in scene.Object
primitive_typeNoType of primitive for create operations. One of: "cube", "sphere", "cylinder", "cone", "plane", "torus", "monkey". Auto-detected from operation if not specified.cube
locationNoWorld-space coordinates (x, y, z) for object placement. Default: (0, 0, 0). Used for all create operations.
scaleNoScale factors along each axis (x, y, z). Default: (1, 1, 1). Applied after object creation.
radiusNoRadius parameter for curved primitives (sphere, cylinder, cone, torus). Default: 1.0. Range: 0.01 to 100.0.
depthNoHeight/depth parameter for 3D primitives (cylinder, cone). Default: 2.0. Range: 0.01 to 100.0.
verticesNoVertex count for curved surfaces (sphere, cylinder). Default: 32. Range: 3 to 256. Higher values = smoother surfaces.
source_nameNoName of source object for duplication operations. Required for "duplicate_object" operation.
distanceNo
thicknessNo
inset_depthNo
bevel_widthNo
bevel_segmentsNo
subdivide_cutsNo
merge_distanceNo
join_namesNo
prefer_sessionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It lists operations including delete_object, but does not disclose side effects (e.g., permanent deletion, scene modification) or prerequisites (e.g., Blender running). The description focuses on capabilities rather than behavioral traits.

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

Conciseness2/5

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

The description is verbose, starting with a meta rationale in caps that is not immediately useful. The core purpose is buried after the rationale. It could be shortened and front-loaded with the actual purpose.

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?

Despite many parameters and operations, the description does not explain return values, error handling, or prerequisites. It lists operations but lacks detail on which parameters apply to which operation. The presence of an output schema is not mentioned, so the agent has no guidance on responses.

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 description coverage is 50%, and the description adds some context (e.g., linking operations to required parameters) but does not significantly enhance understanding beyond the schema. Many parameters have detailed schema descriptions already, so the description provides minimal additional value.

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 clearly states the tool's purpose: 'Create and manipulate mesh objects in Blender with comprehensive primitive support.' It lists many operations, distinguishing this tool as the mesh-specific one among many blender tools. The portmanteau pattern rationale explains consolidation, but the description could be more explicit about the scope.

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 does not provide explicit guidance on when to use this tool vs. alternatives. It includes a 'PORTMANTEAU PATTERN RATIONALE' that explains design but not usage. There is no mention of when to prefer this tool over other blender tools like blender_modifiers or blender_transform.

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/sandraschi/blender-mcp'

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