Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

setup_subdivision_animation

Animate a subdivision surface modifier's viewport levels across frames. Specify object, start/end levels, and frame range to control mesh smoothness over time.

Instructions

Animate a subdivision surface modifier's viewport levels.

Args: object_name: Target object. modifier_name: Name of the subdivision modifier. start_level: Starting subdivision level. end_level: Ending subdivision level. start_frame: Start frame. end_frame: End frame.

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_name": "<object_name>"
    },
    "name": "setup_subdivision_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_frameNo
end_levelNo
object_nameYes
start_frameNo
start_levelNo
modifier_nameNoSubdivision

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full burden of disclosing behavior. It merely says 'Animate' without explaining that it creates keyframes, whether it overwrites existing animation, how it handles the modifier's render vs. viewport levels, or any side effects. The tool's mutating nature is implied but not detailed.

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?

The description is concise: one sentence plus a parameter list. It isn't wordy, and the list is directly relevant even if redundant with the schema. The structure is simple and front-loaded with the purpose. However, the parameter list adds little value beyond the schema, slightly detracting from overall effectiveness.

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 six parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain how the animation is set up (keyframes, interpolation), what the expected outcome is, whether the modifier must exist beforehand, or error conditions. It leaves too much for the agent to infer.

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?

The Args list repeats parameter names from the schema without adding meaning. For example, 'start_level' and 'end_level' are not clarified as integer subdivision levels or that they represent viewport levels specifically. The schema has no descriptions, so the description should compensate, but it doesn't explain units, ranges, or relationships between parameters.

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

Purpose4/5

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

The description states a clear purpose: 'Animate a subdivision surface modifier's viewport levels.' This specifies the verb (animate), the resource (subdivision surface modifier), and the attribute (viewport levels). It distinguishes itself from generic animation tools like set_keyframe or create_walk_cycle by focusing on a specific modifier type, though it doesn't mention the frame range explicitly.

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 provides no guidance on when to use this tool versus alternatives. It doesn't state prerequisites (e.g., the object must have a subdivision modifier), nor does it mention that this is the tool for animating subdivision levels rather than other animation tools. No exclusions or alternative tool references are given.

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