Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_object_info

Retrieve detailed Blender object data—type, location, rotation, scale, modifiers, materials, parent, children, and visibility—to inspect scene structure for modeling and animation tasks.

Instructions

Get detailed information about an object.

Args: object_name: Name of the object.

Returns: Dict with type, location, rotation, scale, modifiers, materials, parent, children, and visibility info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_nameYes

Output Schema

TableJSON 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 are provided, so the description carries the full burden. It does disclose the returned fields (type, location, rotation, scale, modifiers, materials, parent, children, visibility), which confirms it is a non-mutating getter, but it says nothing about behavior on a missing object, name-resolution rules, or cost of a deep hierarchy query.

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 purpose sentence followed by a short Args/Returns block with no filler. Slightly padded because the Returns list duplicates what the output schema already provides.

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?

An output schema exists, so enumerating return fields in the description is redundant but harmless; for a one-parameter read tool this is close to sufficient. The only real gap is the absence of any statement about what happens when the named object does not exist.

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 0%, but there is only one self-evident string parameter, and the description's 'Name of the object' merely restates the schema title 'Object Name'. It adds no naming convention or lookup semantics beyond the obvious.

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 and resource ('Get detailed information about an object'), so the agent knows this is a read-only inspection tool. It does not distinguish itself from siblings like get_scene_info or list_objects, leaving the agent to infer scope from the name alone.

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 when-to-use guidance, no prerequisites (e.g. object must exist / be selected), and no alternatives named among the many sibling inspection tools. The agent must infer that this is the per-object counterpart to get_scene_info.

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