Skip to main content
Glama

modify_modifier

Update an existing Blender modifier's settings by providing the object name, modifier name, and new values.

Instructions

Update modifier settings.

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>",
      "settings": "<settings>"
    },
    "name": "modify_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
settingsYes
modifier_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 behavioral burden, yet it says nothing about permissions, whether changes are reversible, how omitted settings are treated, or what the response contains. For a mutation tool with a nested settings object, this is effectively zero disclosure beyond the word 'Update.'

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 not concise in the useful sense: it is under-specified rather than economical, consuming minimal space while conveying almost no information. There is no structure to front-load because there is only one vague clause.

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?

Given a mutation tool with three required parameters, an open-ended nested settings object, no annotations, and two similarly named name parameters, the definition is nowhere near complete. The existence of an output schema removes the need to document return values, but that does not offset the missing input and behavioral context.

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% and the description adds no parameter meaning. In particular it does not explain the difference between the required "name" and "modifier_name" parameters, nor what keys the free-form "settings" object accepts, leaving all three required parameters semantically opaque.

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 pairs the verb "Update" with the resource "modifier settings," so the general operation is identifiable. However, it does not distinguish this from siblings like apply_modifier or add_modifier, and it never clarifies what 'settings' means or which modifier the parameters target.

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 when-to-use guidance, no mention of alternatives such as apply_modifier or add_modifier, and no prerequisite context (e.g., whether the modifier must already exist). The agent must infer all routing decisions from the tool name 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