blender-fx-mcp

Overview Schema Source Related Servers Discussions Admin

inspect_mesh

Check a 3D model before destruction effects: identify non-closed geometry, volume, concavity, face count, and preview repairs to avoid fracture issues.

Instructions

Diagnose a mesh before fracturing it: closed?, volume, concavity, face count, repair preview. 부수기 전에 모델 상태를 본다. 닫혀 있는지, 부피, 오목한 정도, 면 수, 수리하면 얼마나 나아지는지. 남이 만든 모델을 가져왔을 때 destroy 전에 부르면 문제를 미리 알 수 있다.

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": {
      "target": "<target>"
    },
    "name": "inspect_mesh"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes
`decimate_to`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 20, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description must carry the transparency burden. It lists what the tool inspects, implying a read-only operation, and 'repair preview' suggests it does not modify the mesh. However, it does not explicitly state that it has no side effects or whether it can fail. Partial disclosure but acceptable given the name and wording.

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?

The description repeats the same information in Korean after the English text, adding redundancy without new value. The first sentence is concise and front-loaded, but the repetition lengthens it unnecessarily, reducing conciseness.

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?

While the purpose and usage context are clear, the complete lack of parameter documentation makes it incomplete. The output schema exists, so return values are covered, but an agent cannot correctly call the tool without understanding what to pass in. The description does not compensate for the low schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not mention either parameter ('target' or 'decimate_to') at all. An agent has no idea what these parameters mean or how they affect the inspection, which is a critical gap for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('diagnose') and resource ('mesh') with the explicit context of being called before fracturing. It lists concrete checks (closed, volume, concavity, face count, repair preview) that distinguish it from destructive siblings like 'destroy' and 'explode'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'before fracturing' and 'destroy 전에' (before destroy), giving a clear temporal trigger. It also adds a use case ('when you bring someone else's model'). It does not explicitly exclude any alternative, but the context is strong enough to guide selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.