Skip to main content
Glama

apply_modifier

Applies a specified modifier to a named Blender object, making the modifier's effect permanent for final modeling, export, or rendering.

Instructions

Apply a modifier.

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_name": "<modifier_name>"
    },
    "name": "apply_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
modifier_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/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 of behavioral disclosure and delivers none of it. It does not say whether applying is destructive, whether the modifier must already exist on the object, whether it is reversible, or what state change results.

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?

The single sentence is short but is under-specified rather than concise; there is no front-loaded scope or constraint. Brevity here removes information rather than trimming waste.

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

Completeness1/5

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

Although an output schema exists and need not be explained, this is a mutation-style tool with two undocumented required parameters and zero annotations. The description leaves an agent without enough information to invoke it correctly or predict its effect.

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?

Both parameters are required with 0% schema description coverage, and the description adds no meaning. It does not clarify whether "name" is the target object, the modifier stack, or something else, nor how "modifier_name" is resolved.

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

Purpose2/5

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

"Apply a modifier" restates the tool name and adds no distinguishing detail. With siblings like add_modifier, modify_modifier, and remove_modifier in the same namespace, the agent cannot tell what applying means relative to adding or modifying a 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?

The description gives no when-to-use guidance, no prerequisites, and no exclusions. It does not say how this differs from add_modifier or modify_modifier, leaving the agent to guess from names alone.

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