Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.character_analyze_asymmetry

Read-onlyIdempotent

Analyze character mesh asymmetry by LEFT/RIGHT region and classify each pair as intentional, likely intentional, likely accidental, or unknown using declared tolerances without enforcing symmetry.

Instructions

Mirror asymmetry per region and LEFT/RIGHT pair, classified intentional / likely_intentional / likely_accidental / unknown with the declared thresholds. Symmetry is never enforced.

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_asymmetry"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestNo
object_nameYes
tolerance_fractionNo
intentional_regionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context: the four classification buckets and the explicit note that symmetry is never enforced, clarifying that the tool only reports. However, it does not disclose how thresholds are determined or what happens when regions are missing.

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 tightly written sentences with no obvious waste, front-loading the core action and classification scheme. The structure is efficient, though the phrase 'Mirror asymmetry per region' could be slightly polished for clarity.

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 and annotations cover safety, so return format and side effects need not be repeated. Still, the description leaves key parameter meanings unexplained (manifest, object_name) and does not clarify how regions are identified, which is important for an analysis tool with 4 params and 0% schema coverage.

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% for four parameters, so the schema provides no parameter meaning. The description obliquely references 'regions' and 'declared thresholds' (corresponding to intentional_regions and tolerance_fraction) but says nothing about manifest or object_name, leaving most parameters 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 states a specific analysis verb (mirror asymmetry) and resource (character mesh regions / LEFT-RIGHT pairs), and names the classification categories. It is distinguishable from siblings like character_analyze_silhouette or facial_analyze_asymmetry by scope, though it does not explicitly say 'character mesh' beyond 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?

The description explains what is measured but gives no guidance on when to use this tool versus other analysis tools (e.g., facial_analyze_asymmetry, character_analyze_silhouette). It also omits prerequisites or when-not-to-use conditions.

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