Skip to main content
Glama

get_object_info

Retrieve detailed Blender object data by name—including type, location, rotation, scale, dimensions, modifiers, materials, parent, children, and visibility—to inspect scene objects.

Instructions

Get detailed information about an object.

Args: object_name: Name of the object.

Returns: Dict with type, location (as set), world_location (where it really is after parents, constraints and simulation), rotation, scale, dimensions, modifiers, materials, parent, children, and visibility.

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": {
      "object_name": "<object_name>"
    },
    "name": "get_object_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • removedInput schema / properties / name
      Removed value: -{
      -  "title": "Name",
      -  "type": "string"
      -}
    • addedInput schema / properties / object_name
      Added value: +{
      +  "title": "Object Name",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "object_name"
      +]
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. 'Get' implies a read-only lookup and the Returns block discloses the contents of the response, which is genuinely useful. It does not say what happens for a nonexistent name (error vs empty), nor whether it triggers a depsgraph evaluation, nor permission/context requirements.

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?

Front-loaded one-line purpose followed by Args and Returns blocks. Slightly verbose in the Returns enumeration, but every listed field ('world_location after parents, constraints and simulation') adds meaning.

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?

An output schema exists, so the Returns section is largely redundant, yet the semantic clarification of world_location versus location is worth keeping. The gap that matters for a read tool in a 150-sibling toolset is disambiguation from other inspection tools, and that is absent.

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 coverage is 0% and there is one required parameter; the description's 'Args: object_name: Name of the object' only restates the parameter name. It doesn't note whether the name must be fully qualified, whether collection-scoped lookup is supported, or how ambiguity is resolved.

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 clear verb+resource: retrieve detailed information about an object. It's distinguishable from list_objects (enumeration) and get_scene_info (scene-level) by the word 'object', though the description never names those siblings.

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?

No guidance on when to use this versus get_scene_info, list_objects, get_selection, or list_objects-plus-filtering. An agent must infer that this is the per-object introspection call.

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