Skip to main content
Glama

blender_mesh

Create and manipulate mesh objects in Blender with operations for generating primitives, duplicating, deleting, extruding, beveling, subdividing, and merging.

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
nameNoName for the new object or object to delete. Must be unique in scene.Object
depthNoHeight/depth parameter for 3D primitives (cylinder, cone). Default: 2.0. Range: 0.01 to 100.0.
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.
distanceNo
locationNoWorld-space coordinates (x, y, z) for object placement. Default: (0, 0, 0). Used for all create operations.
verticesNoVertex count for curved surfaces (sphere, cylinder). Default: 32. Range: 3 to 256. Higher values = smoother surfaces.
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
thicknessNo
join_namesNo
bevel_widthNo
inset_depthNo
source_nameNoName of source object for duplication operations. Required for "duplicate_object" operation.
bevel_segmentsNo
merge_distanceNo
prefer_sessionNo
primitive_typeNoType of primitive for create operations. One of: "cube", "sphere", "cylinder", "cone", "plane", "torus", "monkey". Auto-detected from operation if not specified.cube
subdivide_cutsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv0.5.0
    • addedInput schema / properties / bevel_segments
      Added value: +{
      +  "default": 2,
      +  "type": "integer"
      +}
    • addedInput schema / properties / bevel_width
      Added value: +{
      +  "default": 0.1,
      +  "type": "number"
      +}
    • addedInput schema / properties / distance
      Added value: +{
      +  "default": 0.5,
      +  "type": "number"
      +}
    • addedInput schema / properties / inset_depth
      Added value: +{
      +  "default": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / join_names
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / merge_distance
      Added value: +{
      +  "default": 0.001,
      +  "type": "number"
      +}
    • addedInput schema / properties / prefer_session
      Added value: +{
      +  "default": true,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / subdivide_cuts
      Added value: +{
      +  "default": 2,
      +  "type": "integer"
      +}
    • addedInput schema / properties / thickness
      Added value: +{
      +  "default": 0.1,
      +  "type": "number"
      +}
  2. First observedv0.1.0

TDQS

C2.3/5.0
Behavior1/5

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

The description explicitly lists destructive operations such as 'delete_object: Remove objects from scene by name' and 'delete_faces: Delete selected faces', yet the annotations declare destructiveHint=false. This is a direct contradiction. Additionally, the description omits behavioral details like requirements for edit mode or permanence of deletions.

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 opens with a meta 'PORTMANTEAU PATTERN RATIONALE' that is not operationally useful and bloats the entry. The core description is then buried behind this rationale. While the operation list is structured with bullets, the overall length and unnecessary rationale make it less concise and front-loaded.

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?

With 18 parameters and many operations, the description lacks essential context such as prerequisites (e.g., needing an object in edit mode for extrude/inset), selection requirements, coordinate systems, and the mapping of parameters to operations beyond create/duplicate/delete. The output schema exists, so return values need not be explained, but the operational context is still insufficient.

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 parameter description coverage is only 50%. The description adds some value by specifying parameter requirements for create/duplicate/delete operations (e.g., 'create_* require: name'), but it fails to explain many parameters such as distance, thickness, join_names, bevel_width, inset_depth, bevel_segments, merge_distance, prefer_session, and subdivide_cuts, which remain undocumented in both schema and description.

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 creates and manipulates mesh objects in Blender with primitive support, and enumerates specific operations. However, it confusingly claims to consolidate '9 related mesh operations' while listing 18, and does not explicitly distinguish itself from sibling tools like blender_scene or blender_transform.

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 direct guidance is given on when to use this tool versus alternatives. The portmanteau rationale mentions preventing tool explosion, but it does not specify scenarios or exclusions. For a tool with many overlapping siblings, this is a significant gap.

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

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