Skip to main content
Glama
Sign In
cadloop-openscad

cadloop-openscad

by richardofortune
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

echo

Evaluate an OpenSCAD script and return computed values, enabling model inspection without a mesh render.

Instructions

Evaluate a script and return only its ECHO output. Use this to read computed values out of a model without paying for a mesh render.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
sourceNo
definesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that only ECHO output is returned and that it is cheaper than a render, but says nothing about side effects of evaluating a script, which of file/source is required, permissions, or failure behavior.

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?

Two tight sentences, front-loaded with the core action and followed by the usage rationale. Every clause earns its place with no filler.

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. However, with no annotations and three fully undocumented parameters, the description omits the input-selection guidance an agent needs to actually invoke the tool correctly.

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

Parameters1/5

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

Three parameters (file, source, defines) exist with 0% schema description coverage, and the description never mentions any of them. It gives no guidance on the file-vs-source choice or the defines map, so it fails to compensate for the coverage gap.

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 ('Evaluate a script and return only its ECHO output') and explicitly scopes the result to ECHO output. It also differentiates from the sibling 'render' by noting it avoids a mesh render, so an agent can place it 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?

'Use this to read computed values out of a model without paying for a mesh render' gives a clear when-to-use and implicitly positions render as the heavier alternative. It does not state explicit exclusions or when another sibling (check, measure) is preferable, so it stops short of a 5.

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

Deploy Server

Other Tools