Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

sketchup_status

Check the connection status to SketchUp and retrieve mock info before using other tools.

Instructions

Estado de conexión a SketchUp + info mock. Usa esto primero.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, but a status/connection check is inherently a low-risk read and the description makes that role clear. The existence of an output schema means return shape need not be described; the only real gap is no mention of failure modes or whether it performs any action in SketchUp.

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?

Two short sentences with the ordering instruction front-loaded and no wasted wording. The mixed Spanish/English and the vague 'info mock' phrase slightly hurt precision but not length.

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?

For a zero-parameter status tool with an output schema, the essentials are covered, but 'info mock' is never explained and no expectation is set for what a disconnected state means. A single clarifying clause would make this 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. 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 names the resource ('conexión a SketchUp' / SketchUp connection status) and adds a '+ info mock' component, which is vague and unexplained. It is separable from siblings like get_scene_info or eval_ruby, but the second half of the purpose ('info mock') leaves an agent unsure what is actually returned.

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?

'Usa esto primero' gives one explicit directive: call this before the other tools. There is no guidance on when not to use it, how often to poll, or what to do if the status reports disconnected, so usage is only partially specified.

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