Skip to main content
Glama

export_html

Pack a circuit design into one offline HTML file that includes schematic, board, 3D, BOM, fabrication, and model files for easy handoff.

Instructions

Write the design as one HTML file beside the circuit (schematic, board, 3D, BOM, fabrication and model files inside; opens offline). Use it to hand the design to a person as one file.

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>"
    },
    "name": "export_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoProject file, .html
fileYesCircuit file
lookNoAs render's

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The description usefully discloses the side effect and target location — a file is written to disk "beside the circuit" — plus that the result "opens offline," which goes beyond the minimal readOnlyHint=false/destructiveHint=false flags and is consistent with them. It does not say what happens if a file already exists at that path (overwrite vs. fail) or how large/self-contained the bundle is.

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 with the action front-loaded and the contents conveniently parenthesized, with no filler. The parenthetical list is dense but each item carries information about what the export includes.

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 three-parameter, nested-object tool with no output schema, the description covers what is produced, where it lands, and that it works without network access — enough for correct invocation. Gaps around default `out` behavior and the `look` object are minor given full schema coverage.

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 100%, so the three parameters are already documented, and the description adds only the implied default output location ("beside the circuit"). The nested `look` object (mask/silk/finish) is deferred to the schema's "As render's" reference and receives no explanation here, so nothing meaningfully new is added for parameters.

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 ("Write the design as one HTML file") and enumerates the bundled payload (schematic, board, 3D, BOM, fabrication, model files), which clearly sets it apart from single-artifact exporters like export_fabrication or export_model. It stops short of naming those siblings explicitly, so an agent must infer the contrast.

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 it to hand the design to a person as one file" gives a concrete selection context (human handoff, portable single artifact). There are no explicit exclusions or named alternatives for cases where a single-format export is wanted instead.

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