Skip to main content
Glama

get_scene_info

Retrieve detailed information about the current Blender scene, including objects, materials, and settings for AI-assisted 3D modeling workflows.

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. It is decorated with @mcp.tool() for registration, uses get_blender_connection() to communicate with Blender via send_command('get_scene_info'), and returns the scene information as formatted JSON or an error message. The docstring provides the tool description serving as schema.
    @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)}"
  • Usage instruction in the asset_creation_strategy prompt that recommends calling get_scene_info() first to check the current scene state.
    0. Before anything, always check the scene from get_scene_info()
  • Helper function get_blender_connection() used by the tool handler to obtain a connection to the Blender server.
    def get_blender_connection():
        """Get or create a persistent Blender connection"""
        global _blender_connection, _polyhaven_enabled  # Add _polyhaven_enabled to globals
        
        # If we have an existing connection, check if it's still valid
        if _blender_connection is not None:
            try:
                # First check if PolyHaven is enabled by sending a ping command
                result = _blender_connection.send_command("get_polyhaven_status")
                # Store the PolyHaven status globally
                _polyhaven_enabled = result.get("enabled", False)
                return _blender_connection
            except Exception as e:
                # Connection is dead, close it and create a new one
                logger.warning(f"Existing connection is no longer valid: {str(e)}")
                try:
                    _blender_connection.disconnect()
                except:
                    pass
                _blender_connection = None
        
        # Create a new connection if needed
        if _blender_connection is None:
            host = os.getenv("BLENDER_HOST", DEFAULT_HOST)
            port = int(os.getenv("BLENDER_PORT", DEFAULT_PORT))
            _blender_connection = BlenderConnection(host=host, port=port)
            if not _blender_connection.connect():
                logger.error("Failed to connect to Blender")
                _blender_connection = None
                raise Exception("Could not connect to Blender. Make sure the Blender addon is running.")
            logger.info("Created new persistent connection to Blender")
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. While 'Get detailed information' implies a read-only operation, it doesn't specify what information is returned, format, potential errors, or whether this requires Blender to be in a particular state. 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 gets straight to the point with no wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information about what the tool does.

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 no parameters, the description should do more to explain what 'detailed information' includes and how this differs from other information-retrieval tools in the sibling set. The current description leaves too many questions unanswered about the tool's behavior and output.

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 schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose rather than repeating what's already clear from the schema.

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 ('about the current Blender scene'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_object_info' or 'get_hyper3d_status', but the specificity of 'Blender scene' provides reasonable distinction.

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 like 'get_object_info' or 'get_hyper3d_status'. It doesn't mention prerequisites, timing considerations, or any context about what 'current' means in relation to Blender's state.

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