Skip to main content
Glama

export_scene

Export the current scene from Sketchup in a specified format using the Model Context Protocol, enabling streamlined 3D model sharing and integration.

Instructions

Export the current scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoskp

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the export_scene tool. It connects to Sketchup via socket, sends a JSON-RPC request to call the 'export' tool with the specified format, and returns the JSON result.
    @mcp.tool()
    def export_scene(
        ctx: Context,
        format: str = "skp"
    ) -> str:
        """Export the current scene"""
        try:
            sketchup = get_sketchup_connection()
            result = sketchup.send_command(
                method="tools/call",
                params={
                    "name": "export",
                    "arguments": {
                        "format": format
                    }
                },
                request_id=ctx.request_id
            )
            return json.dumps(result)
        except Exception as e:
            return f"Error exporting scene: {str(e)}"
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action but doesn't disclose if this is a read-only operation, what permissions are needed, whether it modifies the scene, what the output entails (e.g., file creation), or any rate limits. This is inadequate for a tool that likely generates external output.

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 extremely concise with a single sentence, 'Export the current scene', which is front-loaded and wastes no words. It directly states the purpose without unnecessary elaboration, earning full marks for efficiency.

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 tool likely performs an export operation (implying file output or data generation), the description is incomplete. With no annotations, no output schema, and minimal behavioral details, it fails to address key aspects like what 'export' produces, where it goes, or how it interacts with the scene. This leaves significant gaps for an AI agent to understand the tool's full context.

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 description doesn't mention parameters, but with only one optional parameter ('format') and 0% schema description coverage, the baseline is high. Since there are zero required parameters, the tool can be used without specifying inputs, making the lack of parameter details less critical. The description doesn't add meaning beyond the schema, but the minimal parameter burden justifies a score above baseline.

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

Purpose3/5

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

The description 'Export the current scene' clearly states the action (export) and target (current scene), but it's somewhat vague about what 'scene' means in this context and doesn't differentiate from sibling tools like 'create_component' or 'transform_component'. It avoids tautology but lacks specificity about the export's nature or format.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an open scene), exclusions, or related tools for other operations like 'get_selection' or 'set_material'. Usage is implied only by the action itself.

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

Related 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/BearNetwork-BRNKC/SketchUp-MCP'

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