Skip to main content
Glama
mikeysrecipes

BlenderMCP

get_object_info

Retrieve detailed information about a specific object in a Blender scene to understand its properties and characteristics 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 main handler function for the 'get_object_info' tool, registered via @mcp.tool() decorator. It connects to Blender, sends the 'get_object_info' command with the object name, and returns the JSON-formatted result or an 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed information' but does not specify what that includes (e.g., object properties, location, type), whether it's read-only, or any potential errors or limitations. This leaves significant gaps in understanding the tool's behavior and output.

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 concise and well-structured: a clear purpose statement followed by a bullet point for the parameter. Every sentence adds value without redundancy, making it easy to understand quickly. The front-loaded purpose statement enhances readability and efficiency.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'detailed information' entails, potential return formats, or error handling. For a tool with no structured output documentation, this leaves too much ambiguity for reliable agent invocation 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 description adds meaningful context for the single parameter 'object_name' by explaining it as 'The name of the object to get information about.' Since schema description coverage is 0%, this compensates well by clarifying the parameter's role. However, it does not detail constraints like case sensitivity or valid object names, 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 tool's purpose: 'Get detailed information about a specific object in the Blender scene.' It specifies the verb ('Get detailed information') and resource ('a specific object in the Blender scene'), making the intent unambiguous. However, it does not explicitly differentiate from its sibling 'get_scene_info', which might retrieve broader scene-level information, so it misses the highest score.

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 does not mention sibling tools like 'get_scene_info' or specify contexts where this tool is preferred over others. Without such guidance, users must infer usage from the tool name and description alone, which is insufficient for optimal tool selection.

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

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