Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_modeling_object

Read a modeling object's world, basis, and parent-inverse matrices plus its parent and selection/active context in Object Mode to inspect Blender scene state.

Instructions

Read modeling-object world/basis/parent-inverse matrices, parent and selection/active context 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_modeling_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden: 'Read' correctly signals a non-mutating operation, and it enumerates the data categories returned, which is genuinely useful. It does not say what happens when the object is not in Object Mode (error vs empty result) or how the snapshot handles objects with no parent or no active selection.

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 short sentences, front-loaded with the returned data before the mode restriction. Dense but no wasted wording; the matrix list could be slightly clearer about ordering but is acceptable as-is.

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?

With no output schema, the description does the important work of enumerating what comes back (three matrix types plus a context snapshot), which is more than most read tools offer. What remains missing is the precondition's failure behavior and the meaning of the lone required parameter.

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?

The single parameter 'name' has zero schema description coverage, and the description never states that the name identifies a modeling object, what happens on a miss, or whether it accepts a partial/unique-prefix match. 'Modeling-object' in the opening clause gives weak implicit context, but the semantics of the required argument remain largely undocumented.

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 ('Read') plus the exact resources returned: world/basis/parent-inverse matrices and a parent/selection/active context snapshot. This is far more precise than a generic 'inspect' label. It stops short of naming which sibling to use instead (e.g. get_object_details), so differentiation is inferred 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Object Mode only' gives a real precondition the agent must satisfy before calling. However, there is no guidance on when to pick this over the similarly named get_object_details or inspect_modeling_geometry, leaving the agent to guess from resource names alone.

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