Skip to main content
Glama
zinin

sketchup-mcp2

by zinin

eval_ruby

Execute Ruby code inside SketchUp to automate 3D modeling tasks. Returns the last evaluated expression; use a final result.to_json for structured output.

Instructions

Evaluate arbitrary Ruby code in SketchUp.

Disabled by default in the Extension Warehouse build. If disabled, the SketchUp side returns JSON-RPC code -32010 with a user-facing message explaining how to enable it. This wrapper surfaces that message as a plain string so the LLM can repeat it to the user verbatim — without the [code] prefix that format_error would otherwise add.

Returns the .to_s of the LAST evaluated expression; stdout (puts) is NOT captured. End scripts with an explicit expression — e.g. a final result.to_json — to get structured data back. Errors return "[code] message" with the Ruby exception class and message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesRuby code to evaluate inside SketchUp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are present, so the description carries full burden for behavioral disclosure. It thoroughly explains disabled-by-default behavior, error handling, return value as .to_s of last expression, lack of stdout capture, and error format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise yet comprehensive, front-loaded with the main purpose, and each sentence adds necessary information without redundancy.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the simple schema with an output schema, the description covers behavior, return values, errors, and configuration status completely.

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?

Schema coverage is 100% with a clear description for the single 'code' parameter. The description adds value by explaining how to structure code (use explicit expression) to get desired output, going beyond the schema.

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?

The description clearly states the tool evaluates arbitrary Ruby code in SketchUp, with a specific verb and resource. It is distinct from sibling tools, none of which execute arbitrary code.

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?

While the description implicitly indicates use for running custom Ruby code, it lacks explicit guidance on when to use this tool versus alternatives, or conditions to avoid it. No exclusionary context is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zinin/sketchup-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server