Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

clear_scene

Deletes all components from the simulated mock scene without affecting the live SketchUp model.

Instructions

Limpia la escena mock (borra todos los componentes). No afecta SketchUp vivo.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does useful work: it discloses the destructive blast radius ('borra todos los componentes') and, more importantly, that the effect is confined to a mock scene and does not touch live SketchUp. What is missing is reversibility (undo/confirmation), what happens when the scene is already empty, and whether the mock scene must exist first.

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?

Two short sentences with zero filler; the destructive behavior is front-loaded and the safety caveat follows immediately. Every clause earns its place, and no schema or annotation content is redundantly repeated.

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?

An output schema exists, so return values need no explanation, and a zero-parameter tool needs little else. The definition is nearly complete for this complexity; only edge-case behavior (empty or absent mock scene) and reversibility are left unaddressed.

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 zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste space restating an empty schema.

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?

States a specific verb and target ('Limpia la escena mock') and immediately resolves scope by parenthesizing what clearing means ('borra todos los componentes'). The mock-vs-live disclaimer further pins the resource, so an agent can tell it apart from delete_component or create_component without inspecting any schema.

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?

Usage is implied rather than stated: it is obviously for resetting the mock scene, and 'No afecta SketchUp vivo' signals this is not the tool for live-model work. However, no sibling alternative is named (e.g. delete_component for a single component, or the live-model tools), and no prerequisites are given, so routing still requires inference.

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