Skip to main content
Glama
ujs204

BlenderMCP

by ujs204

get_scene_info

Retrieve detailed information about the current Blender scene, including objects, materials, and settings, to analyze and manage 3D projects.

Instructions

Get detailed information about the current Blender scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'get_scene_info' MCP tool, registered via the @mcp.tool() decorator. It establishes a connection to the Blender addon, sends the 'get_scene_info' command, and returns the result as formatted JSON.
    @mcp.tool()
    def get_scene_info(ctx: Context) -> str:
        """Get detailed information about the current Blender scene"""
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_scene_info")
            
            # 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 scene info from Blender: {str(e)}")
            return f"Error getting scene info: {str(e)}"
  • The @mcp.tool() decorator registers the get_scene_info function as an MCP tool.
    @mcp.tool()
  • Comment in the asset_creation_strategy prompt recommending the use of get_scene_info() to check the scene before other operations.
    0. Before anything, always check the scene from get_scene_info()
    1. First use the following tools to verify if the following integrations are enabled:
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. While 'Get detailed information' implies a read-only operation, it doesn't specify what 'detailed information' includes, whether there are any rate limits, authentication requirements, or what format the information is returned in. The description is too vague about the actual behavior.

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 a single, efficient sentence that states exactly what the tool does without any unnecessary words. It's appropriately sized for a zero-parameter tool and front-loads the core purpose immediately.

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 a description that's vague about what 'detailed information' actually means, this is incomplete. The agent won't know what to expect from this tool's output or how to interpret the results. Given the complexity of Blender scenes, more context about what information is returned would be helpful.

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 tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could potentially mention that no parameters are required.

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 action ('Get detailed information') and target resource ('current Blender scene'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_object_info' or 'get_hyper3d_status' that also retrieve information from different aspects of the Blender environment.

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, what prerequisites might exist, or how it differs from other information-retrieval tools in the sibling list like 'get_object_info' or 'get_hyper3d_status'.

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/ujs204/CLAUDE-BLENDER-MCP'

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