Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_capture

Destructive

Capture the current SketchUp view as an image for visual review, with optional width, height, and zoom extents; the image supports review but does not certify geometry.

Instructions

Capture the actual current native view for visual review; an image is not a geometry certificate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "sketchup_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
widthNo
heightNo
zoom_extentsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, implying this writes or overwrites something on disk, yet the description never mentions writing a file, overwriting an existing file at `path`, or permission needs. The 'not a geometry certificate' caveat is genuinely useful extra context, but the destructive behavior itself goes undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is good, but the second clause is terse jargon ('geometry certificate') that reads as a warning fragment rather than clear guidance. Efficient but under-explanatory rather than genuinely concise.

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?

An output schema exists so return values need not be explained, but for a destructive file-writing tool with four undocumented parameters the description omits destination/overwrite behavior and parameter meanings. It is not sufficient for an agent to call this correctly without opening the schema and guessing.

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

Parameters1/5

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

Schema description coverage is 0% for four parameters, and the description explains none of them: `path` (destination and overwrite semantics), `width`/`height` (output resolution, defaults 1600x1000), and `zoom_extents` (whether the camera is fit to model before capture) are all left opaque. This is the main failure of the definition.

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 verb 'Capture' plus resource 'current native view' gives a rough idea, but the description never states what is actually produced (an image file written to `path`?) or that it renders the live SketchUp viewport. It is distinguishable from siblings like sketchup_export only by implication, not by an explicit statement.

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?

'For visual review' implies a when-to-use context, and 'an image is not a geometry certificate' signals a when-not (do not use as proof of geometry). However, no alternative tool is named for geometry verification, so the agent must infer routing from sibling names alone.

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