Skip to main content
Glama

get_object_info

Retrieves detailed information for a single Blender object by name, letting AI clients inspect properties, transforms, and data before modeling or rendering.

Instructions

Get detailed info for a single object by name.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/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 it discloses almost nothing. It does not say whether the call errors on an unknown name, whether the name must be exact or case-sensitive, or what categories of detail are returned. The presence of an output schema lightens the return-value burden but not the lookup-failure behavior.

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 front-loaded sentence with zero filler. It is efficient, though its brevity shades into under-specification rather than tight structure.

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

Completeness5/5

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

The tool is a one-parameter read with a defined output schema, so the description needn't explain return values. Still, the omission of failure behavior and sibling differentiation keeps this from being a fully complete definition; a 3 reflects adequate-but-thin coverage for a simple tool.

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 the single 'name' parameter, and the phrase 'by name' largely restates the field title 'Name'. It confirms the object is identified by name rather than index or ID, but adds nothing about exactness, uniqueness, or case handling, which is where the ambiguity actually lies.

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 and resource: 'Get detailed info for a single object by name.' An agent can tell it fetches metadata for one object rather than mutating anything. However, in a family containing get_object_transform, get_active_object, and per-domain info tools like get_camera_info, 'detailed info' is never disambiguated from 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?

There is no when-to-use guidance at all: no prerequisites, no statement of when to prefer this over get_object_transform or get_active_object, and no mention of what to do when the named object is absent. The agent must infer usage purely from the name.

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