Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_physics

Inspect active physics settings for a Blender scene or object, including rigid body world, solver substeps, point cache baking status, and cloth or collision configuration.

Instructions

Inspect active physics configuration in the scene or on a specific object: rigid body world settings, solver substeps, point cache baking status, and cloth/collision settings.

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_physics"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoOptional scene timeline frame to evaluate physics transformations at.
object_nameNoOptional name of target object to inspect. If omitted, all physics objects in scene are reported.
include_cache_infoNoWhether to query point cache baking status and frame ranges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never states that the operation is strictly read-only and non-mutating, nor whether querying point cache baking status is expensive, nor what the report looks like when inspecting the whole scene versus a single object.

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 with the scope stated immediately and no redundant framing. The trailing enumeration is long but each item carries information about what will be reported.

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 inspection tool with no output schema and no annotations, the description says what domains are inspected but not the shape or granularity of the report, and leaves the read-only guarantee unstated. Adequate to call correctly, but thin given the absence of structured behavioral metadata.

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 coverage is 100%, so all three parameters are already documented in the schema. The description echoes two of them ('on a specific object', 'point cache baking status') and adds no semantics beyond that, and it never mentions the frame parameter's evaluation meaning.

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 read verb (Inspect) against a specific resource (active physics configuration) and enumerates the sub-areas covered: rigid body world settings, solver substeps, point cache status, cloth/collision. That enumeration clearly separates it from configure_physics or bake_physics_simulation in spirit, though no sibling is ever named.

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 when-to-use guidance: nothing says to call this before baking, after configuring, or instead of configure_physics/setup_physics. The only conditional in the text ('If omitted, all physics objects in scene are reported') describes a parameter default, not usage selection.

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