Skip to main content
Glama

get_scene_info

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

Instructions

Get detailed information about the current Blender scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the 'get_scene_info' MCP tool handler. It connects to Blender and sends a command to retrieve scene information.
    @telemetry_tool("get_scene_info")
    @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)}")
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. It states 'Get' implying read-only access, but fails to specify what 'detailed information' includes (hierarchy, materials, render settings?), the output format, or potential side effects when no scene is loaded.

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?

Single sentence is efficient and front-loaded, but given the lack of annotations and output schema, the extreme brevity leaves critical behavioral and return-value gaps that a second sentence could have addressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for identifying the tool's basic function, but incomplete regarding the data returned and how it differs from 'get_object_info'. With no output schema provided, the description fails to compensate by describing the expected return structure.

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?

Input schema has zero parameters. Per scoring rules, zero parameters establishes a baseline of 4, as there are no parameter semantics to clarify beyond what the empty schema conveys.

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?

States a clear verb ('Get') and resource ('detailed information about the current Blender scene'). Implicitly distinguishes from sibling 'get_object_info' via scope (scene vs. object), though it does not explicitly clarify what scene-specific data is returned or name alternatives.

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?

Provides no guidance on when to use this versus 'get_object_info' or other data-retrieval siblings, nor mentions prerequisites like having an active Blender scene.

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

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