Skip to main content
Glama
SpiceMCP
by oniondas

generate_design_report

Write a Markdown design report for a simulation run's best design and return the file path; optionally include DC audit, PVT, and Monte Carlo checks that cost LTspice runs.

Instructions

Write a Markdown design report for a run's best design and return its path. Optional checks cost LTspice runs: dc_audit, pvt (supply = source name), monte_carlo=N.

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": {
      "run_id": "<run_id>"
    },
    "name": "generate_design_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNo
pvtNo
plotsNo
run_idYes
supplyNo
dc_auditNo
schematicNo
monte_carloNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description usefully discloses that the tool writes a file, returns its path, and can spend LTspice runs on dc_audit, pvt, or monte_carlo checks. It does not explain output-location or overwrite behavior, whether checks alter run state, or what happens on failure, so important behavioral details remain unstated.

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 two sentences are compact and front-load the artifact, source design, and return value. The second sentence efficiently adds cost and parameter information without filler, although its compressed notation limits how much semantics it can convey.

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

Completeness2/5

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

For an eight-parameter tool with no annotations, no parameter descriptions, and no output schema, the description covers the core operation and return value but leaves several inputs entirely unexplained. The expensive optional checks and multiple artifact-related options call for more complete operational and parameter guidance.

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 description coverage is 0%, and the description only partially compensates: it associates the optional checks with their cost, clarifies that supply is a source name, and indicates that monte_carlo takes an N value. It does not explain out, plots, or schematic, gives no explicit run_id format or selection details, and leaves the exact meaning of dc_audit and pvt largely to inference.

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 gives a specific action and artifact: writing a Markdown design report for a run's best design and returning its path. It clearly conveys the tool's core role, but does not explicitly distinguish it from siblings such as query_run, finish_design, or render_schematic.

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?

The phrase 'for a run's best design' implies that an existing run with a selectable best design is needed. The cost warning helps agents decide whether to enable optional checks, but there is no explicit guidance on when to generate the report, when not to, or which sibling to use for other run-related tasks.

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