Skip to main content
Glama

blender_modifiers

Add, remove, and apply mesh modifiers to Blender objects: subdivision surface, bevel, mirror, solidify, array, boolean, decimate, displacement, wave.

Instructions

Apply and manage mesh modifiers in Blender.

Supports multiple operations through the operation parameter:

  • add_subsurf: Add subdivision surface modifier

  • add_bevel: Add bevel modifier

  • add_mirror: Add mirror modifier

  • add_solidify: Add solidify modifier

  • add_array: Add array modifier

  • add_boolean: Add boolean modifier

  • add_decimate: Add decimation modifier

  • add_displace: Add displacement modifier

  • add_wave: Add wave modifier

  • remove_modifier: Remove a modifier

  • apply_modifier: Apply modifier to mesh

  • get_modifiers: List all modifiers on object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoModifier operation typeadd_subsurf
object_nameNoName of object to modify
modifier_nameNoName of modifier to operate on
modifier_typeNoType of modifier to addSUBSURF
levelsNoSubdivision levels (for subsurf)
render_levelsNoRender subdivision levels
segmentsNoNumber of segments (for bevel, screw)
angle_limitNoAngle limit in degrees (for edge split)
widthNoWidth/thickness (for solidify, bevel)
offsetNoOffset distance (for solidify)
countNoCount/repetitions (for array)
merge_thresholdNoMerge threshold (for mirror)

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 must cover behavioral traits. It does not disclose side effects, error handling, undo behavior, or permissions required for operations like applying modifiers.

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 front-loads the purpose but then includes a lengthy bullet-point list of operations. While comprehensive, it could be more concise by grouping or using a table, and some sentences are verbose.

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?

Given the tool's complexity (12 parameters, multiple operations), the description is adequate but lacks guidance on parameter interplay, defaults, or expected behavior for each operation. An output schema exists but doesn't compensate for missing operational context.

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 the description adds marginal value. It lists operations which imply which parameters are relevant (e.g., levels for subsurf), but this is not explicit and the schema already describes each parameter.

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 it applies and manages mesh modifiers in Blender, with a comprehensive list of supported operations. This differentiates it from sibling tools like blender_mesh or blender_workflow.

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 explicit guidance on when to use this tool vs alternatives. The description lists operations but does not indicate when not to use or suggest better-suited tools for specific tasks, which 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.

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