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 projects.

Instructions

Get detailed information about the current Blender scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_scene_info function acts as the handler for the get_scene_info tool, calling the Blender connection to fetch scene data and formatting it as 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)}"
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Get' implies read-only access, the description fails to specify what 'detailed information' includes (e.g., object counts, render settings, collections) or the return format, leaving critical behavioral traits undocumented.

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?

The description consists of a single, efficient sentence with no redundant words or filler content. It is appropriately front-loaded with the action and target, though it may be overly terse given the lack of output schema.

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 absence of an output schema and annotations in a complex 3D domain (Blender), the description inadequately compensates by failing to describe the structure or content of the returned 'detailed information.' The agent cannot determine what data fields to expect without invoking the tool.

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 input schema contains zero parameters, which establishes a baseline score of 4 per evaluation rules. No parameter description is required or expected given the empty 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 uses a specific verb ('Get') and identifies the target resource ('current Blender scene'). However, it does not explicitly differentiate from sibling tools like `get_object_info`, relying on the agent to infer the distinction between 'scene' and 'object' scope.

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 such as `get_object_info` for specific object data, `execute_blender_code` for custom queries, or `get_viewport_screenshot` for visual inspection. No prerequisites or conditions are mentioned.

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

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