Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

setup_rigid_body_world

Set up the rigid body world and collection in Blender to enable physics simulations. Specify a collection for rigid body objects.

Instructions

Configure the rigid body world and collection.

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

Input Schema

NameRequiredDescriptionDefault
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of discussing side effects or behavioral traits. 'Configure' implies a state-changing operation, but the description does not disclose whether it creates a collection, modifies existing objects, or has specific requirements.

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?

The description is a single concise sentence, immediately stating the action and target. However, it is under-specified, losing some points due to missing useful details.

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?

With no annotations, low complexity (1 param), and an output schema that is not referenced in the description, the tool feels incomplete. It does not explain what 'configure' entails, what the collection parameter does, or what output to expect.

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 description coverage is 0%. The description does not mention the 'collection' parameter at all. The schema only provides a type (string/null), leaving the meaning and effect of the parameter entirely unexplained.

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?

The description uses a clear verb 'Configure' and identifies the specific resource 'rigid body world and collection'. While it doesn't explicitly compare against sibling tools, the tool name itself distinguishes it from related physics/simulation setup tools like setup_cloth_sim or setup_fluid_domain.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or scenarios where a different setup tool might be more appropriate.

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