Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

get_selected_components

Retrieves the currently selected components from a SketchUp scene, acting as a compatibility alias for get_selection.

Instructions

Alias de get_selection para compatibilidad con mhyrr.

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_selected_components"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses essentially nothing about behavior: no indication of whether it is a safe read, whether it has side effects, or what it returns. The equivalence to get_selection is the only behavioral signal, and it depends on the agent already knowing that sibling's semantics.

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?

A single short sentence with no redundant wording, and the key fact (it is an alias of get_selection) is front-loaded. Its brevity is efficient even though the content is thin.

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 the description never says what the alias does or that it takes no arguments. For an agent that has not already read get_selection, the definition is insufficient to decide between the two tools; it also drops into Spanish mid-catalog without explaining the mhyrr context.

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 has zero parameters and the schema confirms an empty properties object, so there is no parameter meaning for the description to add. Baseline 4 applies.

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 description identifies the tool only by reference: 'Alias de get_selection' tells an agent it is a duplicate of the sibling get_selection, but never states what that operation actually does (retrieve the current selection). The differentiation from siblings is achieved by naming get_selection, yet the purpose itself is left as an indirection the agent must resolve elsewhere.

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?

'para compatibilidad con mhyrr' gives a conditional reason to pick this over get_selection: use it in mhyrr-compatibility contexts. That is implied guidance rather than an explicit when-to-use/when-not statement, and no other alternative or prerequisite is mentioned.

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