Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

get_version

Returns the server version and a Python-to-Ruby compatibility verdict, acting as a runtime sanity check that still responds when other tools or connections fail.

Instructions

Return the server version and Python↔Ruby compatibility verdict.

Useful as a runtime sanity probe — always returns a payload, even when the connection or other tools surface errors. The result is a JSON string with fields: python_version, ruby_version, min_compatible_ruby, ruby_min_compatible_python, compatible (bool), error (string | null).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does it well: it discloses the always-returns-a-payload guarantee, including under connection failure, which is the key non-obvious trait of a diagnostic probe. It does not mention latency, authentication needs, or side effects, but the tool is plainly read-only.

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?

Front-loaded with the purpose, then the usage hint, then the payload fields. The field enumeration partially duplicates the output schema, which is mild waste, but it is short enough to read in one pass and nothing is filler.

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 the description needn't restate return fields, yet it does describe error handling ('error (string | null)') and payload guarantees that the schema alone would not convey. Within that richness, the only missing piece is any note on cost/latency or failure modes of the probe itself.

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?

Zero parameters, so the baseline is 4. The description additionally explains the shape of the returned payload, which is the only semantic content this tool has.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return the server version and Python↔Ruby compatibility verdict'), which is clearly distinguishable from every sibling tool (component operations, eval_ruby, viewport screenshots). An agent knows immediately what this returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the tool as a 'runtime sanity probe' usable even when the connection or other tools error, which gives a clear use condition. It stops short of naming when NOT to use it or pointing at alternatives, but for a diagnostic no-arg tool the guidance is sufficient.

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