Skip to main content
Glama

inspect_object

Inspect a Blender object’s mesh counts, transforms, materials, modifiers, constraints, rig, and animation action to verify scene data before editing or rendering.

Instructions

Inspect mesh counts, transforms, materials, modifiers, constraints, rig and animation action.

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": {
      "session_id": "<session_id>",
      "name": "<name>"
    },
    "name": "inspect_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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. It implies a read-only inspection but never states it, and says nothing about what happens if the named object does not exist, whether a live session is required, or how the returned data is shaped. The property list is a scope hint, not behavioral context.

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 compact sentence that front-loads the verb and then lists the inspected facets. Every token carries information and nothing is padded. It is a sentence fragment rather than structured prose, but that is appropriate for its length.

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

Completeness2/5

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

With no annotations, no output schema, and two undocumented parameters, the description is the only source of truth and it covers scope only. An agent still cannot know the return format, error conditions, or session requirements before invoking it. The property list is helpful but insufficient for a tool with this much unstated behavior.

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 two required parameters, so the description must compensate and it does not mention either one. 'name' could be an object name, a path, or a node identifier, and 'session_id' is unexplained — an agent cannot tell whether the name is qualified, case-sensitive, or scoped to a scene. Only the enumeration of inspected properties partially implies what 'name' refers to.

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 gives a specific verb (Inspect) and enumerates exactly which object properties are returned: mesh counts, transforms, materials, modifiers, constraints, rig, animation action. That is far more concrete than a bare 'inspect'. It does not explicitly contrast itself with the sibling inspection tools (inspect_scene, inspect_nodes, inspect_dependencies), so it stops short of a 5.

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 statement of when to use this tool versus inspect_scene, inspect_nodes, or inspect_dependencies, all of which plausibly overlap on object-level data. No prerequisites, no exclusions, no indication of whether it requires an open session first. The agent must infer usage purely from the word 'object'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.