Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.retopology_compare_silhouette

Read-onlyIdempotent

Compares orthographic FRONT, SIDE, THREE_QUARTER, and BACK silhouette masks using shared bounds to compute IoU, disagreement area, and boundary distance in metres.

Instructions

Equivalent orthographic FRONT/SIDE/THREE_QUARTER/BACK ray masks with shared bounds: IoU, disagreement area and symmetric boundary-distance metrics in metres, with configurable gates and raster resolution.

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": {
      "relationship": "<relationship>"
    },
    "name": "production.retopology_compare_silhouette"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
relationshipYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description does add real behavioral context: it renders orthographic ray masks across four canonical views with shared bounds, reports metrics in metres, and notes configurable gates and raster resolution. But it does not say what the gates do (fail the run? tag a report?), how expensive the raster/ray-mask computation is, or what shape of result comes back.

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 dense sentence with no redundancy, which is good for brevity, but the jargon load ('equivalent orthographic ... ray masks with shared bounds') and lack of structure hurt readability for a tool with non-trivial inputs. Front-loading the action or the operand before listing metrics would have helped.

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 explained, but the required 'relationship' parameter and the options bag remain undefined, and there is no context on which assets are compared or when this comparison should be run. For a gated metric-comparison tool, that leaves the agent unable to construct a correct call with confidence.

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 coverage is 0% and both parameters ('relationship', required, and 'options', free-form object) are completely undocumented. The phrase 'configurable gates and raster resolution' hints at what lives inside 'options' but does not name or map any option, and 'relationship' — the one required input — is never explained. The description does not compensate for the coverage 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 description names a specific computation (silhouette comparison across FRONT/SIDE/THREE_QUARTER/BACK orthographic ray masks yielding IoU, disagreement area and boundary distance), which is more descriptive than the tool name alone. However, it never states its operand: which two meshes or assets are compared, or what the required 'relationship' parameter denotes. It reads as a description of the metric output rather than a clear verb+resource action, leaving the core purpose partly 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?

The description offers no when-to-use guidance, no preconditions, and no exclusions. It does not distinguish this tool from nearest neighbours such as production.retopology_compare_source, production.character_analyze_silhouette, production.character_compare_reference, or production.qa_compare_before_after, so an agent has no basis for choosing among them besides the name.

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