Skip to main content
Glama
Sign In
SketchUp MCP untuk Windows

SketchUp MCP untuk Windows

by yonnayy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_selection

Retrieve the IDs, types, and bounding boxes of entities currently selected in SketchUp so you can inspect or process the active selection.

Instructions

List the entities the user currently has selected in SketchUp (id, type, bounds).

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.4.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It conveys that the operation is a read ('List') and hints at the return shape (id, type, bounds), but says nothing about what happens with an empty selection, whether it requires an active model, or any ordering/limits.

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?

A single front-loaded sentence with no filler; the resource and its scope ('currently selected') are stated first, and the trailing field list adds useful detail without padding.

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-value documentation is already covered, and with zero parameters this is a simple read tool. The description is sufficient, though a note about the active-model prerequisite or empty-selection behavior would make it fully complete.

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?

There are zero input parameters, so the baseline is 4. The parenthetical '(id, type, bounds)' describes output fields rather than parameters, which is harmless but not additive to parameter meaning.

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?

States a specific verb (List) and resource (entities the user currently has selected in SketchUp), and even previews the returned fields. It is immediately distinguishable from all siblings (which mutate, export, or evaluate), but it doesn't explicitly name a sibling to differentiate against, so 4 rather than 5.

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?

The phrase 'currently has selected' implies the usage context (inspecting the live selection), but there is no explicit when-to-use, prerequisite (e.g. an open model), or alternative guidance. Adequate but with clear gaps.

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

Deploy Server

Other Tools