Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.animation_analyze_bezier

Read-onlyIdempotent

Analyze Blender Bezier animation curves to distinguish overshoot and contextual tangent issues from expected fast motion, so speed is not flagged as a spike.

Instructions

Handle overshoot and contextual tangent findings; fast motion is not automatically a spike.

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": "production.animation_analyze_bezier"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
object_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds no behavioral context — nothing about what region/curves are inspected, what 'finding' means, or what 'handle' entails (the verb 'Handle' is ambiguous and mildly at odds with a pure analysis tool, though not a strict contradiction).

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?

It is a single short sentence with no padding, which is good, but it front-loads an interpretive caveat rather than the tool's purpose, and the clause is too compressed to be parseable without the tool name.

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?

An output schema exists, so return values need not be described. However, for a two-parameter tool with 0% schema coverage and a cryptic, purpose-free description, an agent cannot reliably decide when to call it or what to pass — the definition is materially incomplete.

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% for two parameters, including a required 'object_name' string and an untyped 'options' object with additionalProperties. The description supplies zero information about either parameter, so an agent has no basis for constructing the options payload.

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

Purpose2/5

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

The description never states what the tool does. 'Handle overshoot and contextual tangent findings' gestures at a topic (bezier tangent analysis) but uses no verb+resource framing and does not distinguish this from siblings like production.animation_repair_bezier or production.animation_analyze_fcurves. An agent must infer purpose entirely from the tool name.

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 or when-not-to-use guidance, and no alternative tool is named. The clause 'fast motion is not automatically a spike' is a hint about interpreting results, but it does not tell an agent when to call this tool or what to do with the output.

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