Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

setup_fluid_domain

Set up a fluid simulation domain in Blender, with the option to designate an emitter to generate fluid.

Instructions

Template: Set up fluid simulation with domain and optional emitter.

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": {
      "domain": "<domain>"
    },
    "name": "setup_fluid_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
emitterNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose side effects, prerequisites, or whether the tool creates or modifies objects. 'Set up' is vague about the operational impact on the given domain mesh or emitter.

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 a single, front-loaded sentence with no filler. The 'Template:' prefix is minor noise, but the core instruction is immediately clear and appropriately concise for a two-parameter 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?

For a setup tool with no annotations and 0% parameter coverage, the description omits crucial context such as what a 'domain' object must be, how the emitter is used, and any side effects. Though an output schema exists, it does not compensate for the missing behavioral and parameter guidance.

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%, and the description merely names 'domain' and 'optional emitter' without explaining their roles, types, or requirements. It adds minimal semantics beyond the parameter names, failing to compensate for the lack of schema documentation.

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 the tool's function: 'Set up fluid simulation with domain and optional emitter.' It uses a specific verb ('set up') and resource ('fluid simulation'), and the mention of 'domain' and 'optional emitter' distinguishes it from sibling tools like setup_cloth_sim or setup_rigid_body_world.

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

Usage Guidelines3/5

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

The description implies usage for fluid simulation scenarios but provides no explicit when-to-use guidance or alternatives. There is no mention of when to prefer this over other physics setup tools, resulting in only implied usage context.

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