Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

get_scene_info

Retrieves current SketchUp scene information, attempting live SketchUp data and falling back to mock data when unavailable.

Instructions

Info de la escena actual — intenta SketchUp, fallback a mock.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuinely important trait: it attempts SketchUp first and falls back to mock data, warning the agent that results may be synthetic. Beyond that it omits everything else — whether it is read-only, whether it touches the live model, and what happens when neither backend is available. That single disclosure is real value but insufficient coverage for an unannotated tool.

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?

One short sentence with the fallback caveat right after the resource, so the reader hits the important warning immediately. It is efficiently sized, though the terseness edges into under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 spelled out, and the zero-parameter surface keeps the tool simple. What remains missing is the scene scope and how the sketchup-vs-mock distinction affects the caller's interpretation of results, which the description only gestures at.

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 the schema leaves nothing to clarify and the description rightly spends no words on arguments. The baseline of 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 verb is implicit and the resource is only loosely named: 'Info de la escena actual' tells an agent it retrieves something about the current scene, but not which fields or scope (selection vs. whole model). It does not distinguish itself from siblings such as get_selection, sketchup_status, or get_selected_components, so an agent must guess which read tool applies.

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 and no exclusion of alternatives; the only contextual cue is the implicit 'current scene' framing. Nothing tells the agent whether to call this before a mutation, or how it differs from sketchup_status for connection checks.

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