Skip to main content
Glama

blender_modifiers

Apply and manage mesh modifiers in Blender, with support for subdivision, bevel, mirror, solidify, array, and boolean operations.

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 carry the full burden. It describes operations but fails to disclose behavioral traits such as side effects of applying/removing modifiers, undo behavior, or error conditions. For a 12-parameter tool, more transparency is needed.

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

Conciseness4/5

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

The description is well-structured with a bullet list of operations and clear grouping. It is slightly verbose with repeated 'Add' prefixes, but front-loads the main purpose effectively.

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 12 parameters and no annotations, the description covers operations but lacks contextual guidance on when to choose specific modifiers or how parameters interact. An output schema exists but is not shown, which could have compensated.

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 baseline is 3. The description adds value by grouping operations and listing per-modifier parameters, but does not significantly augment the parameter descriptions already present in the schema.

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 'Apply and manage mesh modifiers in Blender' and lists all supported operations with examples, making its purpose distinct from sibling tools like blender_mesh or blender_materials.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists operations but does not explicitly guide when to use this tool versus alternatives like blender_mesh or blender_transform. Usage is implied through the tool's name and operation list, but no exclusions or when-not-to-use guidance are provided.

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