Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.animation_polish_curves

Plans animation curve polish before applying it to compatible rigs, with explicit mapping, retained source Actions, and separate technical QA and artistic review.

Instructions

animation_polish_curves: high-level M6 unit. Plan first, apply=false by default; generation is the immutable plan.json reference. Explicit mapping and compatible body rig required. Source Actions retained; technical QA and temporal artistic review are distinct. options carries declared stage parameters, thresholds or visual review; unsupported adapters return concrete errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "production.animation_polish_curves"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
briefNo
intentNo
optionsNo
generationNo
object_nameNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already say it is a non-destructive, non-idempotent write, but the description adds substantive behavior the annotations cannot: apply defaults to dry-run, generation is an immutable plan.json reference, source Actions are retained, and unsupported adapters fail with concrete errors. These are meaningful operational facts an agent needs before mutating animation data.

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

Conciseness3/5

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

Sentences are short and the plan-first constraint is front-loaded, but the opening 'high-level M6 unit' is noise and phrases like 'Explicit mapping' and 'technical QA and temporal artistic review are distinct' are cryptic without context. It is terse rather than efficiently informative.

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?

For a 7-parameter, deeply workflow-dependent tool with zero schema documentation and nested free-form objects (brief, intent, options), the description is not complete enough: four parameters are unexplained and internal terms like 'M6' are never grounded. The existing output schema covers return values, but the input story remains thin.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load. It usefully explains apply (dry-run default), generation (immutable plan reference), and options (stage parameters, thresholds, visual review), but leaves brief, intent, object_name, and operation_id completely undefined.

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 name implies curve polishing, but the description never states a concrete action; 'high-level M6 unit' is internal jargon that conveys nothing to a new agent. It does reveal a plan-then-apply workflow and prerequisites, which is some purpose, but it never distinguishes polish_curves from siblings like animation_refine_arcs, animation_cleanup_fcurves, or facial_polish_curves.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real guidance on sequencing ('Plan first, apply=false by default') and hard prerequisites ('Explicit mapping and compatible body rig required'). However, no alternatives or when-not-to-use conditions are named among the very similar animation fix/refine siblings.

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