Skip to main content
Glama

get_object_info

Retrieve detailed information about a specific object in a Blender scene to analyze its properties and structure.

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' MCP tool. It connects to Blender via a persistent socket connection, sends the 'get_object_info' command with the object name parameter, and returns the result as formatted JSON string. Includes error handling.
    @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 this is a read operation ('Get detailed information'), but doesn't describe what information is returned, format of the response, error conditions, or any constraints (like whether the object must exist in the current scene). The description is minimal and lacks behavioral context.

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?

The description is appropriately concise with two sentences that directly address purpose and parameters. The parameter documentation is clearly formatted. No unnecessary information is included, though it could be slightly more front-loaded with usage context.

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?

For a tool with no annotations, no output schema, and multiple sibling tools in a complex domain (3D modeling), the description is insufficient. It doesn't explain what 'detailed information' includes, how results are structured, or how this differs from related tools like 'get_scene_info'. The agent would lack critical context for proper tool selection and result interpretation.

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?

The schema has 0% description coverage, but the description explicitly documents the single parameter ('object_name: The name of the object to get information about'), adding meaningful context beyond the schema's basic type information. Since there's only one parameter and it's fully documented in the description, this compensates well for the schema gap.

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 detailed information') and resource ('about a specific object in the Blender scene'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_scene_info', which might provide broader scene information rather than object-specific details.

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 sibling tools like 'get_scene_info' (which might provide broader scene context) or clarify whether this is for retrieving metadata, properties, or other object details. No usage context or exclusions are provided.

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/wenyen-hsu/blender-mcp'

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