Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_force_field

Inspect active physics force fields in a Blender scene or on a named object to verify simulation settings.

Instructions

Inspect active physics force fields in the scene or on a specific object.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name of the force field object to inspect. If omitted, all force fields in the scene are reported.
object_nameNoAlias for name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose a meaningful trait beyond the schema: only *active* force fields are reported, and omitting the name widens scope to the whole scene. However, it never states read-only/non-mutating behavior explicitly and says nothing about what properties are returned or whether the operation has side effects.

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?

A single front-loaded sentence with no filler; the scope distinction is delivered immediately with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, zero-required-parameter read tool with full schema coverage and no output schema, the definition covers what is needed to invoke it correctly. The only notable gap is the lack of an explicit statement that it is non-mutating and of what fields the inspection yields.

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% and the schema already documents both parameters, including the fact that object_name is an alias for name and that omission returns all force fields. The description adds no syntax, format, or matching-behavior detail beyond that, so the baseline 3 applies.

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 specific verb+resource combination ("Inspect active physics force fields") and states scope (whole scene vs. a specific object). It implicitly contrasts with configure_force_field (mutation) and the broader inspect_physics, but never names them, so sibling differentiation is left to inference.

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?

Usage is only implied: the word "Inspect" and the scene-vs-object scope suggest a read-only query tool. There is no explicit statement of when to choose this over inspect_physics or configure_force_field, and 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