Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

get_selection

Returns selected SketchUp entities so MCP clients can inspect the current selection before editing or transforming objects.

Instructions

Entidades seleccionadas (mock o SketchUp).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden and discloses almost nothing. It does not state that this is a read-only accessor, what happens when the selection is empty, or how the mock backend differs from a live SketchUp connection — the one piece of context it does offer (mock vs. SketchUp) is left unexplained.

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?

It is certainly short and front-loaded, but the brevity is under-specification rather than economy — a single fragment that leaves the core action implicit. The parenthetical is the only information-dense element and it introduces more ambiguity than it resolves.

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 described, and the zero-parameter surface keeps complexity low. Still, for a tool whose entire identity hinges on the mock-versus-SketchUp distinction and on overlap with a near-identical sibling, the description leaves an agent unable to decide when or why to invoke it.

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 document and the baseline of 4 applies. Nothing in the description misrepresents the parameter surface.

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?

"Entidades seleccionadas (mock o SketchUp)" identifies the resource (currently selected entities) and hints at two possible backends, but it is a noun phrase with no verb and no indication of what the tool actually does with them (fetch, list, describe). It also does not distinguish itself from the sibling get_selected_components, which reads as an equally plausible choice for the same task.

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 when-to-use guidance at all: nothing says whether to call this before or after other selection tools, or why one would choose it over get_selected_components. The parenthetical "mock o SketchUp" implies a backend distinction but never explains the condition under which each applies.

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