Skip to main content
Glama

generate

Render a parametric OpenSCAD model into an STL file with optional PNG preview, applying presets or per-call parameter overrides and returning artifact filename plus STL metrics.

Instructions

Render STL and optionally PNG preview in artifacts dir. Preset defaults apply unless preset is given; per-call params override the preset. Unknown presets or params are rejected. Unknown licenses require allow_unknown_license=True. Returns artifact filename and STL metrics.

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": {
      "model_id": "<model_id>"
    },
    "name": "generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
presetNo
previewNo
model_idYes
allow_unknown_licenseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose validation behavior (unknown presets or params are rejected), the license gate, the preset/override precedence, and what is returned (artifact filename and STL metrics). It omits render cost/duration, whether previews overwrite existing artifacts, and permission requirements.

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?

Four dense sentences with no filler, front-loaded with the primary action and its outputs. The telegraphic style is efficient, though the precedence rule and the license rule could be split more clearly for scanning.

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?

There is no output schema, and the description compensates by stating the return value (artifact filename plus STL metrics). With no annotations and a 0%-covered five-parameter schema, though, the description should say more about what goes inside 'params' and about model_id before an agent can call this confidently.

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

Parameters2/5

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

Schema coverage is 0%, so the description must explain all five parameters. It covers preset, preview and allow_unknown_license through the precedence and license sentences, but 'params' is a free-form object with additionalProperties=true and the description never says which keys are valid, which is the single largest ambiguity. model_id is also left entirely unexplained.

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?

The description names the concrete output artifacts: renders STL and optionally a PNG preview into the artifacts directory. That is a specific verb-plus-resource statement despite the generic tool name 'generate'. It does not need sibling differentiation here because list_models is clearly a different concern.

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?

Useful conditional rules are given: preset defaults apply unless a preset is supplied, per-call params override the preset, and allow_unknown_license=True is required for unknown licenses. However, there is no statement of when to use this tool versus an alternative or when a preset should be preferred over explicit params, so guidance stays implicit.

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