Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_armature

Inspect armature rest bones, hierarchy, roll angles, pose transforms, constraints, and snapshot ID to validate rig structure and posing; optionally evaluate a specific frame.

Instructions

Inspects armature rest bones, bone hierarchy, roll angles, pose transforms, pose constraints, and snapshot ID.

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": {
      "armature_name": "<armature_name>"
    },
    "name": "inspect_armature"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoOptional scene timeline frame to evaluate pose transforms at.
include_poseNoWhether to include pose transforms and bone constraints (defaults to True).
armature_nameYesName of the armature to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 and does not meet it: it never says the operation is read-only, whether evaluating pose transforms at a frame triggers a depsgraph update or has side effects, what 'snapshot ID' implies for caching or staleness, or how large the returned data may be. The presence of a snapshot ID hints at a stateful mechanism without explaining it.

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?

One dense sentence with zero filler and the resource front-loaded after the verb; every listed item is a concrete facet. The trade-off is that the comma list reads as an inventory rather than explaining which facet matters when.

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 no output schema, no annotations, and three parameters, the description partially compensates by listing the data categories the caller gets back. It still leaves the return shape, the meaning of snapshot ID, and any side effects of pose evaluation unexplained for a tool whose whole job is reporting state.

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%, so both optional parameters are already documented in the schema, and the description adds little syntactic or semantic detail beyond naming 'pose transforms' and 'pose constraints', which loosely maps to include_pose. Baseline 3 applies when the schema does the heavy lifting.

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 (inspects) plus the resource (armature) and enumerates the exact facets returned: rest bones, bone hierarchy, roll angles, pose transforms, pose constraints, snapshot ID. That is far more specific than a generic 'inspect' tool, though it never distinguishes itself from neighboring inspectors such as inspect_scene_data or inspect_modeling_object.

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?

The enumerated facets imply the situations where this tool is the right pick (when bone/rig data is needed), and the schema hints at optional pose evaluation. But there is no explicit when-to-use statement, no exclusion telling the agent when another inspector is better, and no prerequisite about needing an existing armature.

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