Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_fluid_simulation

Inspect active Mantaflow fluid simulations to review Domain, Flow, and Effector settings plus cache state, helping diagnose issues and verify fluid setup.

Instructions

Inspect active Mantaflow fluid simulations (Domain, Flow, Effector) and cache state.

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": "inspect_fluid_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoAlias for object_name.
approvedNoDEPRECATED / UNTRUSTED.
object_nameNoOptional name of the object with fluid modifier to inspect. If omitted, all fluid objects in the scene are reported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Inspect' and 'active' communicate a read-oriented, active-simulation scope, and cache state is called out as reported, but it doesn't state what happens with inactive or partially baked sims, whether anything is mutated, or what errors look like.

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?

A single front-loaded sentence of roughly the right size with no filler. It packs the verb, resource, object types, and cache state efficiently.

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?

For a zero-required-parameter read tool with no output schema, the definition covers what is inspected and the all-objects default is in the schema. However, it never sketches the shape of the reported state (per-object fields, cache status values), leaving the agent guessing at the return content.

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 100%, with object_name documented as optional and reporting all fluid objects when omitted, so the description adds nothing beyond the schema baseline. It also doesn't mention the deprecated/alias parameters.

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?

States a specific verb ('Inspect') and resource ('Mantaflow fluid simulations'), naming the three object types (Domain, Flow, Effector) and cache state. This distinguishes it clearly from configure_fluid_simulation and bake_physics_simulation without needing to reference them by name.

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 word 'active' implies a scope constraint on which simulations are inspected, and 'inspect' implies read-only usage, but there is no explicit statement of when to use this versus configuring or baking. No prerequisites or exclusions are given.

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