Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_modifier

Reorder modifiers in Blender's modifier stack by moving them up or down. Specify the object, modifier, and direction to adjust stack order.

Instructions

Move a modifier up or down in the stack. Direction: UP or DOWN.

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": "<object>",
      "modifier": "<modifier>",
      "direction": "<direction>"
    },
    "name": "move_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYes
modifierYes
directionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior, but it only states the action. It does not explain behavior at stack boundaries (e.g., moving an already-top modifier), whether the operation is reversible, or any side effects. It also fails to define valid values for 'direction' besides the hint.

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

Conciseness5/5

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

Two compact sentences with the core action and the key direction parameter immediately conveyed. No unnecessary words or repetition, and the 'Direction: UP or DOWN' is a clear, structured hint.

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?

The tool has no annotations and a 0% schema description coverage, so the description must carry the full context. While the action is clear, missing parameter details, usage context, and boundary behavior make it incomplete for a likely mutation operation.

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

Parameters2/5

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

Schema coverage is 0%, so the description must clarify parameters. It only adds meaning for 'direction' ('UP or DOWN'), leaving 'object' and 'modifier' ambiguous. No hints about identifiers or accepted formats.

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?

The description uses a specific verb ('Move') and resource ('modifier') with clear scope ('up or down in the stack'), which unambiguously distinguishes it from related modifier tools like set_modifier_property or apply_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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it reorders modifiers, nor does it explain how it differs from set_modifier_property or reorder_constraint, leaving the agent to infer usage.

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