Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

get_object_details

Retrieve transform, geometry, material, modifier, and mesh statistics for a Blender object by exact name to inspect or validate scene data.

Instructions

Retrieve detailed transform, geometric, and modifier data for a specific object by name: location, rotation (Euler), scale, bounding box, dimensions, parent, assigned collections, mesh vertex/polygon statistics (if mesh), assigned material names, and modifier stack.

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": "get_object_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact name of the object to inspect.
include_materialsNoWhether to return names of materials linked to slots.
include_modifiersNoWhether to return the modifier stack summary.
include_mesh_statsNoWhether to calculate vertex, edge, and polygon counts for mesh objects.
include_custom_propertiesNoWhether to inspect custom properties stored on the object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies a read-only inspection operation and the description discloses conditional output like mesh statistics only for mesh objects, but it does not state error behavior when the named object is missing, whether the operation has side effects, or performance implications of the include_* flags.

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?

The description is a single front-loaded sentence with no filler. The long enumeration is dense but each listed data category helps an agent understand the return contents, though the list could be more scannable.

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?

There is no output schema, so the description must communicate return values, and it does list many of them. However, it omits custom properties even though include_custom_properties is a parameter, and it does not describe error behavior for a missing object or the effect of disabling optional includes.

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 all five parameters are already documented in the schema. The description adds context about what kinds of data can be returned but does not explain the include_materials, include_modifiers, include_mesh_stats, or include_custom_properties switches beyond what the schema already says; baseline 3 is appropriate.

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 ('Retrieve') and resource ('detailed transform, geometric, and modifier data for a specific object by name') and enumerates the data categories returned. It does not explicitly distinguish this tool from nearby inspection siblings such as inspect_modeling_object or get_scene_summary, so it falls 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?

It implies retrieval by exact object name but gives no explicit when-to-use guidance, no exclusions, and no alternatives such as inspect_modeling_object or get_scene_summary. An agent must infer when this tool is preferable to other inspection tools.

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