Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.facial_polish_curves

Plan facial polish curve edits first, then apply semantic intent to timed facial actions via NLA tracks while preserving the source body action and requiring phoneme timing for speech.

Instructions

facial_polish_curves: M7 facial unit. Evidence-based semantic mapping (never names only); plan first, apply=false by default; facial is the immutable plan.json reference. Candidates are new Actions evaluated through NLA tracks; the body Action is never modified. Speech needs explicit timed phonemes/visemes (TIMING_INPUT_REQUIRED otherwise). Technical QA and artistic review stay separate.

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.facial_polish_curves"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
briefNo
facialNo
intentNo
optionsNo
object_nameNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior4/5

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

Beyond the annotations (which declare non-readonly, non-destructive, non-idempotent), the description discloses meaningful behavior: candidates are written as new Actions via NLA tracks, the body Action is never modified, and speech input without timed phonemes/visemes raises TIMING_INPUT_REQUIRED. It also notes QA and artistic review are separate steps. These are substantive traits not encoded in structured fields, though the failure/return contract is still only partially described.

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?

The text is compact and clause-dense with no filler sentences, and the plan-first/apply-default rule lands early. But the leading name restatement and the opaque 'M7 facial unit' and '(never names only)' parentheticals cost space without adding information an agent can act on.

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?

This is a 7-parameter, zero-coverage mutation tool with an output schema (so return values are covered), yet the description leaves five parameters entirely undefined and doesn't explain what brief/options/intent should contain. For a high-complexity facial animation tool in a 300-sibling suite, the behavioral framing is helpful but the calling contract is under-specified.

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 description coverage is 0% and all seven parameters are cryptically named (brief, intent, options, object_name, operation_id, facial, apply). The description explains only two of them: apply defaults to false, and facial is 'the immutable plan.json reference'. intent, brief, options, object_name, and operation_id carry no meaning anywhere, so the description does not compensate for the schema gap.

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 opening 'facial_polish_curves: M7 facial unit' merely restates the name plus an unexplained internal code, and the actual verb (polishing facial animation curves in a plan/apply workflow) is only inferable from the 'plan first' and 'candidates are new Actions' clauses. It does hint at scope (facial vs. body Action) which helps against siblings like animation_polish_curves, but no single sentence plainly says what it produces.

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?

'plan first, apply=false by default' implies a dry-run-then-apply workflow, which is real usage guidance. However, it never names alternatives such as facial_refine, facial_analyze_curves, or animation_polish_curves, nor states when polishing curves is the wrong choice, leaving sibling selection to inference.

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