Skip to main content
Glama

add_modifier

Adds a specified modifier to a Blender object using its name and modifier type, enabling automated modeling adjustments through MCP.

Instructions

Add a modifier to an object.

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": {
      "name": "<name>",
      "modifier_type": "<modifier_type>"
    },
    "name": "add_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
settingsNo
modifier_nameNo
modifier_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses almost nothing. It does not say whether the modifier is added live or applied, whether the target object must be active or selected, whether an existing modifier stack is affected, or what happens when modifier_type is invalid.

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

Conciseness2/5

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

It is a single short sentence with no filler, but this is under-specification rather than conciseness. The one sentence adds no information beyond the tool name it accompanies.

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

Completeness2/5

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

With four undocumented parameters, no annotations, and several overlapping sibling tools, the definition should do substantial work to be callable correctly. The presence of an output schema covers return values, but nothing else about this mutation tool is explained.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description contributes no information about any of them. The distinction between name, modifier_name, and modifier_type, and the structure of settings, is left completely unexplained despite being the main source of invocation ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ("Add a modifier to an object"), so the basic purpose is inferable. However, it is essentially a restatement of the tool name and does nothing to separate it from nearby siblings like apply_modifier, modify_modifier, or remove_modifier.

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?

There is no guidance on when to use this tool versus apply_modifier, modify_modifier, or create_geometry_nodes_modifier, nor any prerequisites such as object selection or context requirements. The agent must infer its place in the workflow entirely from the name.

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