Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.retopology_budget

Read-onlyIdempotent

Sets configurable triangle target, min, and max budgets with per-region absolute, percentage, or density-weight allocations, and reports when protected-region floors cannot be met.

Instructions

Configurable triangle target/min/max and region absolute/percentage/density-weight allocations. Protected-region floor produces an explicit safe-impossibility report.

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

Input Schema

NameRequiredDescriptionDefault
optionsNo
object_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds domain behavior by noting that protected-region floors produce an explicit safe-impossibility report, but it does not explain whether that report is an error condition, a normal return, or how options affect computation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two dense, front-loaded sentences with no filler. The core configuration dimensions and the special safe-impossibility behavior are both stated immediately.

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 and annotations exist, so return values and safety do not need repetition. However, with 0% schema description coverage, the description is thin on options structure and omits routing guidance against several retopology siblings, leaving meaningful gaps for an agent.

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%, and the schema exposes only object_name plus an opaque options object. The description partially compensates by naming likely option categories (triangle target/min/max and region absolute/percentage/density-weight allocations), but it does not explain the structure of options or clarify object_name beyond its name.

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 (retopology triangle budget) and the configurable dimensions (target/min/max, region allocation modes), plus the protected-region floor behavior. It is clear but does not use a direct verb or distinguish itself from sibling tools like retopology_plan or retopology_priority_map.

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 use this tool rather than retopology_plan, retopology_priority_map, or retopology_optimize_region, and no prerequisites or exclusions. Usage is only inferable from the tool 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