Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_modifier

Attach a non-destructive modifier to a mesh object in Blender, enabling adjustable geometry effects like subdivision, mirroring, arrays, and bevels without permanently changing the mesh.

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

A3.9/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 non-destructive nature and implies stacking via 'modifier stack', and contrasts with booltool's immediate application. It does not cover prerequisites (e.g., object mode), side effects on existing modifiers, or error conditions.

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?

Well-structured with purpose first, a useful TIP, then args and returns. The enum list is repeated from the schema, adding unnecessary length, but overall it is appropriately sized and front-loaded.

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?

Given no annotations and a present output schema, the description covers purpose, usage tip, parameter meanings, and return shape. It lacks details on object mode requirements or modifier interaction, but is sufficient for an agent with basic Blender knowledge to invoke it.

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 description coverage is 0%, so the description must compensate. It labels object_name and modifier_type and clarifies that name is optional, but the explanations are largely tautological with parameter names and the enum list duplicates the schema. It does not explain what each modifier type does.

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 scopes it with 'non-destructive workflow'. The TIP explicitly differentiates it from the booltool_* siblings for boolean operations, so an agent can tell them apart.

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?

Provides explicit when-to-use guidance for the BOOLEAN case, naming the alternative booltool_* tools and the condition (want non-destructive modifier stack). However, it offers no guidance for other modifier types or against siblings like subdivide_mesh or apply_modifier.

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