Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

eval_ruby

Executes arbitrary Ruby code in SketchUp to inspect or modify scenes, and returns mock information when SketchUp is unavailable.

Instructions

Ejecuta Ruby arbitrario en SketchUp. Si no hay SketchUp, mockea con info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "eval_ruby"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the fallback behavior (mocking with info when SketchUp is absent), which is real added context. However, it says nothing about side effects persisting, whether the code mutates the open model, error handling, or any safety constraints — significant gaps for an arbitrary-code-execution 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?

Two short sentences with the core action front-loaded and the fallback condition immediately after. No padding, though the terseness contributes to the missing behavioral detail.

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 explained. Still, for a tool that runs arbitrary code with no annotations, the definition omits whether execution affects the live model and how failures surface — the mock note only partially compensates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter with 0% schema description coverage. The description implies the parameter is arbitrary Ruby source, which adds a little meaning, but offers no detail on what form the code should take or what context it runs in.

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 and resource: executing arbitrary Ruby inside SketchUp. It is immediately distinguishable from the sibling scene/component tools, though it does not name any alternative to route away from.

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?

Usage is only implied by 'arbitrary Ruby', which signals the tool is for code execution rather than the structured scene operations the siblings offer. There is no explicit when-to-use or when-not-to-use guidance, and no comparison to alternatives.

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