Skip to main content
Glama
opslon

BlenderMCP

by opslon

get_viewport_screenshot

Capture screenshots of the Blender 3D viewport for documentation, progress tracking, or sharing visual updates during modeling workflows.

Instructions

Capture a screenshot of the current Blender 3D viewport.

Parameters:

  • max_size: Maximum size in pixels for the largest dimension (default: 800)

Returns the screenshot as an Image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_sizeNo

Implementation Reference

  • The 'get_viewport_screenshot' tool handler, which captures a screenshot from the Blender viewport by sending a command to the Blender addon and decoding the returned base64 image data.
    def get_viewport_screenshot(ctx: Context, max_size: int = 800) -> Image:
        """
        Capture a screenshot of the current Blender 3D viewport.
        
        Parameters:
        - max_size: Maximum size in pixels for the largest dimension (default: 800)
        
        Returns the screenshot as an Image.
        """
        try:
            blender = get_blender_connection()
    
            result = blender.send_command("get_viewport_screenshot", {
                "max_size": max_size,
                "format": "png"
            })
    
            if "error" in result:
                raise Exception(result["error"])
    
            # Decode base64 image data received from addon
            image_bytes = base64.b64decode(result["image_data"])
            img_format = result.get("format", "png")
    
            return Image(data=image_bytes, format=img_format)
    
        except Exception as e:
            logger.error(f"Error capturing screenshot: {str(e)}")
            raise Exception(f"Screenshot failed: {str(e)}")
Behavior3/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. It states the action ('Capture') and return type ('Returns the screenshot as an Image'), but lacks details on permissions needed, whether it's read-only or modifies state, error conditions, or performance characteristics (e.g., if it pauses rendering). It adequately describes the core behavior but misses nuanced operational context.

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 front-loaded with the core purpose, followed by a brief parameter explanation and return statement. Every sentence earns its place with no redundant or verbose language, making it highly efficient and easy to scan.

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

Completeness4/5

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

Given the tool's low complexity (1 optional parameter) and no output schema, the description is mostly complete: it states the action, parameter meaning, default, and return type. However, without annotations or output schema, it lacks details on error handling, image format, or viewport state requirements (e.g., must be in a 3D view), leaving minor gaps for an agent to infer.

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 schema description coverage is 0%, so the description must compensate. It explains the single parameter 'max_size' as 'Maximum size in pixels for the largest dimension' and provides the default value (800), adding clear meaning beyond the schema's title and type. However, it doesn't specify constraints (e.g., minimum/maximum values) or how aspect ratio is handled, leaving some gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Capture a screenshot') and target resource ('current Blender 3D viewport'), distinguishing it from all sibling tools which involve downloading assets, generating models, getting statuses, or importing assets. The verb+resource combination is precise and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a screenshot of the Blender viewport is needed, but provides no explicit guidance on when to use this tool versus alternatives (e.g., other screenshot methods or tools for different visual outputs). There are no exclusions or prerequisites mentioned, leaving usage context somewhat open-ended.

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

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