Skip to main content
Glama

get_object_info

Retrieve detailed scene data for any Blender object by name, enabling AI-assisted 3D modeling and object manipulation through the BlenderMCP server.

Instructions

Get detailed information about a specific object in the Blender scene.

Parameters:

  • object_name: The name of the object to get information about

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_nameYes

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers and implements the get_object_info tool. It retrieves object information by sending a command to the Blender addon and returns the result as formatted JSON.
    @mcp.tool()
    def get_object_info(ctx: Context, object_name: str) -> str:
        """
        Get detailed information about a specific object in the Blender scene.
        
        Parameters:
        - object_name: The name of the object to get information about
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_object_info", {"name": object_name})
            
            # Just return the JSON representation of what Blender sent us
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting object info from Blender: {str(e)}")
            return f"Error getting object info: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a 'get' operation for information, implying read-only behavior, but doesn't disclose any behavioral traits like error handling, permission requirements, rate limits, or what happens if the object doesn't exist. For a tool with no annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose in the first sentence, followed by a clear parameter explanation. Every sentence earns its place with no wasted words. It's appropriately sized for a simple tool.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter, but lacks details on return values, error conditions, or behavioral context. For a read-only info tool, this is the bare minimum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 1 parameter and 0% schema description coverage, the description compensates by explaining 'object_name' as 'The name of the object to get information about.' This adds meaningful context beyond the bare schema. However, it doesn't specify format constraints or examples, preventing a perfect score.

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 clearly states the verb 'Get' and the resource 'detailed information about a specific object in the Blender scene.' It distinguishes from siblings like 'get_scene_info' by specifying object-level rather than scene-level information. However, it doesn't explicitly contrast with all siblings, so it's not a perfect 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use 'get_object_info' vs 'get_scene_info' or other sibling tools, nor does it specify prerequisites or exclusions. This leaves the agent without contextual usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/spranjal3301/final-year-project'

If you have feedback or need assistance with the MCP directory API, please join our Discord server