Skip to main content
Glama

add_modifier

Add a named modifier to a Blender mesh object and choose its type to build non-destructive modeling stacks for subdivision, mirroring, arrays, bevels, and booleans.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object_name": "<object_name>",
      "modifier_type": "<modifier_type>"
    },
    "name": "add_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
object_nameYes
modifier_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / modifier_type / enum
      Previous 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"
      -]New value: +[
      +  "ARRAY",
      +  "BEVEL",
      +  "BOOLEAN",
      +  "BUILD",
      +  "CAST",
      +  "CORRECTIVE_SMOOTH",
      +  "CURVE",
      +  "DATA_TRANSFER",
      +  "DECIMATE",
      +  "DISPLACE",
      +  "EDGE_SPLIT",
      +  "EXPLODE",
      +  "HOOK",
      +  "LAPLACIANDEFORM",
      +  "LAPLACIAN_SMOOTH",
      +  "LATTICE",
      +  "MASK",
      +  "MESH_DEFORM",
      +  "MIRROR",
      +  "MULTIRES",
      +  "NORMAL_EDIT",
      +  "OCEAN",
      +  "REMESH",
      +  "SCREW",
      +  "SHRINKWRAP",
      +  "SIMPLE_DEFORM",
      +  "SKIN",
      +  "SMOOTH",
      +  "SOLIDIFY",
      +  "SUBSURF",
      +  "SURFACE_DEFORM",
      +  "TRIANGULATE",
      +  "UV_PROJECT",
      +  "UV_WARP",
      +  "VERTEX_WEIGHT_EDIT",
      +  "VERTEX_WEIGHT_MIX",
      +  "VERTEX_WEIGHT_PROXIMITY",
      +  "WARP",
      +  "WAVE",
      +  "WEIGHTED_NORMAL",
      +  "WELD",
      +  "WIREFRAME"
      +]
  2. 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"
      +]
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It discloses the key behavioral trait that the modifier is added non-destructively (and that booleans are not applied immediately), and mentions a confirmation return. It omits prerequisites (must the object be a mesh? what happens on invalid type/object?), modifier ordering, and failure behavior.

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?

Purpose and the boolean routing tip are correctly front-loaded, and the Args block is easy to scan. But the long enumeration largely duplicates the schema enum and does so inaccurately, so it adds bulk rather than value.

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?

An output schema exists, so the return-value sentence is redundant but harmless. The main gap is that a mutation tool with no annotations gives no indication of required object state, error conditions, or interaction with an existing modifier stack — enough to attempt a call, not enough to call confidently in edge cases.

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?

With 0% schema coverage, the description must compensate, and it does define all three parameters and their roles. However it states modifier_type 'Must be one of' a list of 29 values that omits 13 values present in the schema enum (BUILD, DATA_TRANSFER, EXPLODE, LAPLACIANDEFORM, MULTIRES, OCEAN, UV_PROJECT, UV_WARP, WARP, NORMAL_EDIT, VERTEX_WEIGHT_EDIT/MIX/PROXIMITY), making the enumeration misleading rather than merely incomplete.

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?

Specific verb plus resource ('Add a modifier to a mesh object') and an explicit scope qualifier ('non-destructive workflow'). It also distinguishes itself from the booltool_auto_* siblings and the apply/remove modifier tools, so an agent can identify it 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 Guidelines4/5

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

The TIP gives a concrete when/when-not rule for the BOOLEAN case (use booltool_auto_* for immediate application, add_modifier only for a non-destructive stack). It does not address alternatives for other modifier types (e.g. add_multires_modifier, add_essentials_modifier, apply_modifier), so guidance is strong but not exhaustive.

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