Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_particle_system

Inspect active emitter particle systems and evaluated particle states on objects, optionally at a specific frame or for a named object/system.

Instructions

Inspect active emitter particle systems and evaluated particle states on objects.

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

Input Schema

NameRequiredDescriptionDefault
nameNoAlias for object_name.
frameNoOptional frame number to evaluate simulated particles at.
object_nameNoOptional name of the object whose particle systems to inspect. If omitted, all particle systems across the scene are reported.
system_nameNoOptional specific particle system name to inspect.

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 disclosure burden, and it gives almost none. It does not say whether evaluating particles at a frame is read-only or side-effecting (frame evaluation can change current scene state), whether it is expensive/slow, or what permissions are needed. 'Inspect' hints at non-destructive behavior but this is never confirmed.

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 no filler; the core action and scope come first. It is efficient, though its brevity leaves the gaps noted in the other dimensions rather than being genuinely complete.

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?

With four optional parameters, no annotations, and no output schema, the description should describe what comes back (per-system records, counts, evaluated state fields) and any cost or side effects of frame evaluation. It only gestures at return content with 'particle systems and evaluated particle states', leaving the agent to guess at the response shape.

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%, including the fallback behavior when object_name is omitted, so the schema does the heavy lifting and baseline 3 applies. The description's phrase 'evaluated particle states' loosely connects to the frame parameter but adds no format, default, or interaction detail beyond the schema.

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 specific resources (active emitter particle systems and evaluated particle states), and the word 'inspect' cleanly separates it from the mutating sibling configure_particle_system. It never names that sibling or any other alternative, so the differentiation is inferred from vocabulary rather than stated.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative for the configuration/mutation case. The only directional signal is 'active' emitter systems, which implies a scope filter but is not framed as a usage rule.

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