Skip to main content
Glama

get_object_info

Retrieve detailed scene data for a specific 3D object in Blender, enabling AI-assisted modeling and analysis.

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. It connects to Blender via get_blender_connection(), sends a 'get_object_info' command with the object_name parameter, and returns the JSON-formatted result or an error message.
    @telemetry_tool("get_object_info")
    @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)}"
  • The @mcp.tool() decorator registers the get_object_info function as an MCP tool. The @telemetry_tool decorator adds telemetry tracking.
    @telemetry_tool("get_object_info")
    @mcp.tool()
  • The docstring provides the tool description and parameter schema: object_name (str). The function signature also defines the input/output types.
    """
    Get detailed information about a specific object in the Blender scene.
    
    Parameters:
    - object_name: The name of the object to get information about
    """
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get detailed information') but doesn't describe what information is returned, format of response, error conditions, or any performance characteristics. The description is minimal beyond stating the basic operation.

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 extremely concise with zero wasted words. It uses a clear two-sentence structure: first stating the purpose, then documenting the single parameter. Every sentence earns its place and the information is front-loaded appropriately.

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 0% schema description coverage, the description is insufficiently complete. While it states the basic purpose and documents the parameter, it doesn't describe what 'detailed information' includes, the response format, or any behavioral aspects needed for effective use.

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 explicitly documents the single parameter 'object_name' with a clear explanation ('The name of the object to get information about'). With 0% schema description coverage and only 1 parameter, this provides good semantic context beyond the bare schema, though it doesn't elaborate on naming conventions or constraints.

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 with a specific verb ('Get detailed information') and resource ('a specific object in the Blender scene'). It distinguishes from some siblings like 'get_scene_info' (which likely gets scene-level info) but doesn't explicitly differentiate from all possible read operations.

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 this tool is appropriate compared to 'get_scene_info' or other information-retrieval tools, nor does it specify prerequisites or exclusions.

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

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