Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_modifier_stack

Reads an object's ordered modifier properties and visibility, plus base/evaluated topology counts and an optimistic concurrency snapshot in Object mode to verify stack state before edits.

Instructions

Read ordered finite modifier properties and visibility, base and evaluated topology fingerprints/counts, plus an optimistic concurrency snapshot. Object mode only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "inspect_modifier_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it signals a read-only operation, restricts scope to object mode, narrows results to finite (non-procedural) modifiers, and discloses that a concurrency snapshot is returned for optimistic locking. It omits error behavior and permission requirements, which keeps it short of a 5.

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?

Two dense sentences with the returned payload enumerated first and the mode restriction last; no filler. The phrasing is jargon-heavy ("ordered finite modifier properties", "optimistic concurrency snapshot") but each clause carries information.

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 one-parameter read tool with no output schema, the description does reasonably well at enumerating what comes back. The critical gap is the meaning of the required "name" argument, which is documented nowhere else and is the one thing an agent must get right to invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter "name", and the description never clarifies whether that name identifies the object, the modifier stack, or an individual modifier. The only hint is "Object mode only," which does not resolve the ambiguity an agent needs before calling.

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 ("Read") and names the resource (the modifier stack) plus the exact contents returned: ordered modifier properties, visibility, base/evaluated topology counts, and a concurrency snapshot. It does not, however, differentiate itself from the sibling inspect_modifiers, which an agent would likely find confusingly close in 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?

"Object mode only" gives one meaningful applicability constraint, and "Read" implies a pre-edit inspection role alongside edit_modifier_stack/apply_modifier. But there is no explicit statement of when to choose this over inspect_modifiers, nor any prerequisite guidance.

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