Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_modifier

Add a modifier to a mesh object for non-destructive editing in Blender. Supports types like SUBSURF, MIRROR, ARRAY, and BEVEL.

Instructions

Add a modifier to a mesh object (non-destructive workflow).

TIP: For BOOLEAN type, consider using booltool_auto_union/difference/intersect/slice instead: they apply the boolean immediately and handle cutter cleanup automatically. Only use add_modifier with BOOLEAN when you want a non-destructive modifier stack.

Args: object_name: Name of the object to add the modifier to. modifier_type: Type of modifier. Must be one of: SUBSURF, MIRROR, ARRAY, BEVEL, BOOLEAN, SOLIDIFY, DECIMATE, REMESH, WIREFRAME, SHRINKWRAP, SMOOTH, EDGE_SPLIT, TRIANGULATE, WEIGHTED_NORMAL, SIMPLE_DEFORM, LATTICE, CURVE, CAST, WAVE, DISPLACE, SCREW, SKIN, MASK, WELD, CORRECTIVE_SMOOTH, LAPLACIAN_SMOOTH, SURFACE_DEFORM, MESH_DEFORM, HOOK. name: Optional custom name for the modifier.

Returns: Confirmation dict with modifier details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
object_nameYes
modifier_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / modifier_type / enum
      Added value: +[
+  "ARRAY",
+  "BEVEL",
+  "BOOLEAN",
+  "CAST",
+  "CORRECTIVE_SMOOTH",
+  "CURVE",
+  "DECIMATE",
+  "DISPLACE",
+  "EDGE_SPLIT",
+  "HOOK",
+  "LAPLACIAN_SMOOTH",
+  "LATTICE",
+  "MASK",
+  "MESH_DEFORM",
+  "MIRROR",
+  "REMESH",
+  "SCREW",
+  "SHRINKWRAP",
+  "SIMPLE_DEFORM",
+  "SKIN",
+  "SMOOTH",
+  "SOLIDIFY",
+  "SUBSURF",
+  "SURFACE_DEFORM",
+  "TRIANGULATE",
+  "WAVE",
+  "WEIGHTED_NORMAL",
+  "WELD",
+  "WIREFRAME"
+]
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral trait — the tool builds a non-destructive modifier stack rather than applying immediately — which is the critical distinction from booltool siblings. It also asserts a return ('Confirmation dict with modifier details'), though the output schema already covers returns. Gaps remain: no mention of whether the modifier must be applied later, side effects on existing stacks, or failure modes (e.g., wrong modifier_type for the object).

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?

Front-loaded with the core action, then the sibling-routing TIP, then Args in a clean structured list. The modifier_type enumeration is long but necessary given the enum. Slight redundancy between the enumerated types in the description and the schema enum.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations exist, so the description must supply behavioral context, and it does the most important part via the non-destructive framing and the booltool alternative. With an output schema present, the return-value sentence is not strictly needed. It is largely complete for a 3-param tool, missing only edge-case behavior (undo/reversibility, interaction with existing modifiers).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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. It does reasonably well: it explains each of the three params (object_name, modifier_type, name) and enumerates all 29 valid modifier_type values, matching the enum. It doesn't clarify that object_name must reference an existing mesh (vs. curve/lattice), but the essential semantics are covered.

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?

States a specific verb and resource ('Add a modifier to a mesh object') and immediately distinguishes the non-destructive semantics from the destructive booltool_* siblings. An agent can tell exactly what this does without opening the schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative (booltool_auto_union/difference/intersect/slice) and the condition that selects it versus this tool ('only use add_modifier with BOOLEAN when you want a non-destructive modifier stack'). This is exactly the when/when-not/alternatives pattern.

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