Skip to main content
Glama

get_object_info

Retrieve detailed information about a specific object in a Blender scene by providing its name, enabling users to access object properties and data for 3D modeling workflows.

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 for the 'get_object_info' tool, decorated with @mcp.tool() for registration. It connects to Blender via get_blender_connection(), sends the 'get_object_info' command with the object name, and returns the JSON-formatted result or error message.
    @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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is to 'get' information, implying a read-only operation, but doesn't specify permissions, error handling, or output format. This leaves gaps in understanding how the tool behaves beyond its basic function.

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 appropriately sized and front-loaded, with a clear purpose statement followed by a brief parameter explanation. Every sentence earns its place without redundancy or unnecessary detail, making it efficient for quick understanding.

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

Completeness2/5

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

Given the tool's complexity (single parameter, no annotations, no output schema), the description is incomplete. It doesn't explain what 'detailed information' includes, how errors are handled, or provide examples, which could hinder an AI agent from using it effectively without additional context.

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?

The description adds minimal semantics by naming the parameter 'object_name' and stating it's 'the name of the object to get information about'. Since schema description coverage is 0%, this provides some value, but it doesn't explain format constraints, examples, or what constitutes a valid object name in Blender context.

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', making the purpose explicit. However, it doesn't distinguish from sibling tools like 'get_scene_info' or 'get_viewport_screenshot', which also retrieve information but for different resources.

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 is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this is for object metadata versus scene-wide details (compared to 'get_scene_info') or visual snapshots (compared to 'get_viewport_screenshot'), leaving usage context implied but unspecified.

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/drrodingo-del/BlenderMCP'

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