Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

export_scene

Export a SketchUp scene to JSON, OBJ, SKP, or GLB, or generate a mock export for testing.

Instructions

Exporta escena mock o pide a SketchUp que exporte. Formatos: json, obj, skp, glb.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
formatNojson

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only hints at a dual behavior ('mock or ask SketchUp') without explaining what determines which path is taken. It does not say whether files are written to disk, where they land, whether output is overwritten, or what permissions/connection state are required.

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?

One short sentence with the action and the format list front-loaded; nothing is padded. The compact 'mock or asks SketchUp' phrasing trades some clarity for brevity, but there is no filler.

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?

An output schema exists, so return values need not be described. However, for a two-parameter export tool with zero annotation coverage, the description leaves out where output goes, how mock mode differs from real export, and what the format values imply for the path parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and no enums are defined, so the description must compensate. It does supply the accepted values for the format parameter (json, obj, skp, glb), which is genuine added meaning, but the path parameter is left entirely unexplained — no indication of what it means, whether it is a directory or filename, or what the empty default implies.

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 states a specific verb and resource ('Exporta escena') and enumerates the supported formats (json, obj, skp, glb), which clearly separates it from siblings like get_scene_info, screenshot, or clear_scene. The only blur is the dual mode ('mock' vs. asking SketchUp to export), which leaves the actual behavior ambiguous.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites such as whether SketchUp must be running or whether a path must be supplied. The format list hints at use cases but is not an instruction about when to invoke it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.