Skip to main content
Glama

export_model

Export a board and its parts alongside the circuit as one 3D model file—STEP for mechanical CAD or GLB for 3D viewers; unfinished designs included.

Instructions

Write the board and its parts as one 3D model file beside the circuit: a STEP file for mechanical CAD (parts as boxes) or a GLB file a 3D viewer turns (the board as made). An unfinished design is written too.

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": {
      "file": "<file>",
      "format": "<format>"
    },
    "name": "export_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoProject file, e.g. cad/board.step
fileYesCircuit file
lookNoglb only, as render's
formatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries most of the behavioral load and does it well: the file is written 'beside the circuit', geometry is simplified ('parts as boxes'), and 'an unfinished design is written too' warns that no completeness check blocks output. It does not say whether an existing file at the target path is overwritten, which is the one notable gap.

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 sentences, front-loaded with the action and followed by the format tradeoff and the edge case, with no filler. The phrasing is slightly convoluted ('a GLB file a 3D viewer turns') but nothing is wasted.

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?

For a 4-parameter export tool with no output schema and minimal annotations, the definition covers what is produced, where it lands, the two format modes, and the unfinished-design case. Only overwrite/path-collision behavior for `out` is left unexplained.

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?

Schema coverage is 75%, so the baseline is 3. The description adds real meaning about what the `format` values produce (STEP as boxes vs GLB as the board as made) but says nothing about `out`, `file`, or the nested `look` object, leaving those entirely to the schema.

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 a specific verb and resource ('write the board and its parts as one 3D model file') and explains the two output variants: a STEP file for mechanical CAD with parts as boxes, or a GLB for viewers. It does not differentiate itself from export siblings such as export_fabrication or export_package, so it stops short of a 5.

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?

It implicitly guides format selection by pairing step with 'mechanical CAD' and glb with 'a 3D viewer turns', which gives a usable when-to-pick-each signal. However, there is no explicit when-not guidance and no alternative export tools are named or contrasted.

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