Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.character_analyze_proportions

Read-onlyIdempotent

Measures and evaluates character proportions against humanoid, creature, or custom references, separating deviation, confidence, and interpretation without forcing stylized or non-human designs to normalize.

Instructions

Proportion measurements (HUMANOID, CREATURE or CUSTOM) with measurement, informational reference, deviation, confidence and interpretation kept separate. Never recommends normalizing a stylized or non-human design.

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

Input Schema

NameRequiredDescriptionDefault
profileNoHUMANOID
manifestNo
object_nameYes
custom_referenceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: it explains the tool separates raw measurement from informational reference and interpretation, and states an explicit non-recommendation policy for stylized/non-human designs, which is exactly the kind of output-philosophy detail an agent needs to trust the results.

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?

Two tight sentences with no filler, and the measurement-scope statement is front-loaded. The first sentence is a dense noun phrase rather than a clean action statement, a minor structural weakness but nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 needn't be described, and the annotations cover safety. However, with four parameters at 0% schema coverage and no usage context, an agent still has to guess what object_name targets and how manifest/custom_reference are supplied before it can call the tool correctly.

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 compensate. It does partially by naming the profile values HUMANOID, CREATURE and CUSTOM, but object_name, manifest, and custom_reference (which evidently pairs with the CUSTOM profile) are never explained, leaving half the inputs undocumented.

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 names the resource (proportion measurements) and scopes it via the three named profiles (HUMANOID, CREATURE, CUSTOM), and enumerates what the output separates (measurement, reference, deviation, confidence, interpretation). It is clear but does not explicitly contrast itself with adjacent analyzers like character_analyze_silhouette or character_analyze_asymmetry, so sibling differentiation is left implicit.

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 statement of when to run this versus other character analyzers, nor any prerequisite such as needing a reference or manifest. The only guidance is a negative policy ("Never recommends normalizing a stylized or non-human design"), which constrains interpretation but does not route the agent between tools.

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