Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_spice_run

Runs pure SPICE netlists through the Multisim kernel and returns parsed result data for each requested analysis command, enabling DC, AC, and transient simulations as JSON.

Instructions

走 Multisim 内核的命令通道跑一张纯网表,返回每个分析的结果数据。

与原理图仿真完全独立:不依赖探针和仪器,只要先用 msim_open 打开任意 .ms14(空白基底即可)建立 COM 上下文。流程:写 deck → 内核执行 → 解析每个 write 出来的 ASCII raw → JSON。

netlist SPICE 网表文本(纯 ASCII,首行是标题注释,末行 .end 可省) commands 分析命令列表,如 ["op", "tran 0 3m", "ac dec 50 10 10meg"]; 只接受分析/绘图命令,其它命令会被拒绝 outdir 结果目录(不能含空格);deck 和 plotN.raw 都写在这里

返回每条命令对应的 plotname/列名/行数据(复数列自动拆成 dB+相位)。

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": {
      "netlist": "<netlist>",
      "commands": "<commands>",
      "outdir": "<outdir>"
    },
    "name": "msim_spice_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
outdirYes
netlistYes
commandsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the required COM session, that files (deck and plotN.raw) are written to disk, that outdir must not contain spaces, that non-analysis commands are rejected, and that complex columns are auto-split into dB+phase. It does not say whether existing files in outdir are overwritten or what happens on kernel failure, which are the remaining behavioral gaps.

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?

The purpose sentence is front-loaded, followed by a short independence note, a flow line, then a compact per-parameter block. Every line carries information, though the mixed prose/parameter layout and the trailing return-format sentence make it slightly denser than necessary.

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-required-parameter tool with no annotations, no output schema and 0% schema description coverage, the description covers prerequisites, flow, parameter formats and the return shape (plotname/column names/row data per command). Only error/failure behavior and file-overwrite semantics are left unspecified.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate and it does for all three parameters: netlist is described as plain ASCII with a title comment on line 1 and an optional .end; commands is given concrete example values and a whitelist restriction; outdir is given a format constraint (no spaces) plus what gets written there. This is meaning well beyond the bare string/array types in the schema.

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?

The description states a specific verb and resource (run a pure netlist through the Multisim kernel command channel) and immediately scopes it: '与原理图仿真完全独立:不依赖探针和仪器'. That explicitly separates it from the schematic-based simulation siblings (msim_run_ac/msim_run_dc/msim_run_tran) without the agent having to open any 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?

It gives a hard prerequisite (msim_open must first open any .ms14, even a blank one, to establish the COM context) and the internal flow (write deck → kernel executes → parse ASCII raw → JSON). It also states a usage constraint (only analysis/plot commands are accepted, others are rejected). It stops short of naming the schematic-based alternative tools explicitly, so the routing is implied rather than spelled out.

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