Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.physics_generate_hair_secondary

Inspect, propose, or apply hair secondary physics to isolated candidates while preserving the body and face, with fixed plans and explicit QA and review gates.

Instructions

Inspect, propose, or execute physics_generate_hair_secondary on isolated secondary candidates. Body/face preserved. apply defaults false; fixed physics plan and explicit QA/review gates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "production.physics_generate_hair_secondary"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
briefNo
intentNo
optionsNo
physicsNo
object_nameNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that: work is confined to isolated secondary candidates with body/face preserved, and applies are gated by a fixed physics plan plus QA/review steps. However, 'fixed physics plan' is unexplained jargon and the description never says what state changes on execute or whether results are reversible.

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?

Three short sentences with the mode set stated first and the constraint/default second; nothing is padded. The telegraphic grammar ('apply defaults false') costs a little readability but the length is well matched to the tool.

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, but for a non-idempotent, non-read-only tool with 7 fully undocumented parameters the description leaves too much open: no prerequisite plan handoff, no routing to the dozens of physics siblings, and no explanation of the QA/review gates it vaguely references.

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% across 7 parameters, so the description must carry the burden and it does not: only 'apply defaults false' is addressed, while brief, intent, options, physics, object_name and operation_id get no mention at all. An agent cannot tell what 'physics' or 'object_name' should contain from either source.

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?

It states the tool operates on 'isolated secondary candidates' and can inspect, propose, or execute, but the core resource ('execute physics_generate_hair_secondary') is a verbatim restatement of the tool name, so the domain (hair secondary physics) is only inferable from the name. 'Body/face preserved' adds useful scope, and 'hair' vs 'cloth'/'accessory' siblings is never mentioned, so differentiation is left to the identifier.

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?

Three modes are listed (inspect/propose/execute) but there is no guidance on when to pick each, what prerequisites are needed (e.g. a plan from physics_plan_hair), or when to prefer physics_generate_soft_secondary or physics_generate_secondary_bones. Only the apply default is stated, which is a parameter fact rather than usage guidance.

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