Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

screenshot

Captures the current SketchUp scene as an image for inspection or export, using a live SketchUp connection and a configured output directory; falls back to a mock when unavailable.

Instructions

Captura de SketchUp. Requiere SketchUp vivo y SCREENSHOT_DIR configurado, si no mock.

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": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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 does disclose genuinely useful context: a live SketchUp instance and a configured SCREENSHOT_DIR are required, and otherwise a mock is returned. It stops short of saying what the mock means, where the output goes, or how errors surface when SketchUp is unreachable.

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?

Two short sentences, zero filler, with the prerequisites front-loaded. It is efficient rather than padded, though the telegraphic style (mixed-language, fragments) costs some readability.

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?

For a zero-parameter tool with both a complete input schema and an output schema, the description covers the essential environmental prerequisites. It is still thin on what the capture actually contains and what the mock fallback returns, which an agent needs to interpret the result correctly.

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 tool takes no parameters, so there is no parameter meaning for the description to add; baseline 4 applies. Schema coverage is 100% and an output schema exists, so nothing further is needed here.

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?

"Captura de SketchUp" identifies the resource (SketchUp) and the general act of capturing, so an agent can infer it produces a screenshot. However, it is a bare noun phrase with no scope: it does not say whether it captures the current viewport, the whole model, or a specific file, and it offers no differentiation from siblings.

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 when-to-use guidance is given and no alternatives are named. The only conditional information is an environment prerequisite, which is more a runtime constraint than a trigger for selecting this tool over another.

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