Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_build

Generate a complete Multisim 14 .ms14 file from a JSON circuit spec, placing components, wiring nets, and attaching voltage probes in one step.

Instructions

一步到位:按电路描述生成完整 .ms14(元件 + 连线 + 探针 + 落盘)。

spec 结构: { "path": "E:\work\rc_lpf.ms14", "components": [ {"ref": "V1", "kind": "signal_ac", "value": 1, "at": [180, 360]}, {"ref": "R1", "kind": "resistor", "value": 1000, "at": [360, 360]}, {"ref": "C1", "kind": "capacitor", "value": 1e-6, "at": [540, 360]}, {"ref": "GND1", "kind": "ground", "at": [360, 540]} ], "nets": [ {"name": "in", "pins": ["V1.1", "R1.1"]}, {"name": "out", "pins": ["R1.2", "C1.1"], "probe": true}, {"name": "0", "pins": ["C1.2", "V1.2", "GND1.1"]} ] }

"at" 可省略(自动网格布局)。probe=true 的网络会自动挂电压探针。

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": {
      "spec": "<spec>"
    },
    "name": "msim_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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, and it does disclose two useful behaviors: 'at' can be omitted in favor of automatic grid layout, and probe=true automatically attaches a voltage probe. However, it does not say whether an existing file at 'path' is overwritten, what happens when a referenced pin does not exist, or what the tool returns on success.

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 one-line purpose statement is front-loaded, and the JSON example is a dense but efficient way to convey a nested schema that the input schema leaves wide open. The explanatory tail about 'at' and probe belongs right after the example, and there is no filler.

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?

Given a complex nested spec, no output schema, and no annotations, the definition is decent but leaves real gaps: the valid 'kind' values are shown only by four examples (signal_ac, resistor, capacitor, ground), with no reference to msim_list_parts or msim_add_part for the full set, and overwrite/error behavior is unstated. An agent still has to guess at supported component kinds, which is the highest-risk unknown for a build tool.

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?

The single spec parameter has 0% schema coverage and is an open nested object, so the description must do all the work -- and it does, providing a complete worked example of the path/components/nets structure, naming the fields ref, kind, value, at, pins, and probe, and explaining the two optional behaviors. This is about as much compensation for schema coverage as a description can provide.

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 gives a specific verb-and-resource pair -- generate a complete .ms14 file -- and spells out the full scope: components, wiring, probes, and writing to disk. The '一步到位' (one-step) framing separates it from the incremental siblings such as msim_add_part and msim_connect without the agent needing to open any of their schemas.

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 one-step framing implies that this is the batch path as opposed to the incremental add/connect/save path, but it never explicitly says when to use it or which alternatives exist. It also does not state that it should be preferred only for new designs or only when the whole circuit is known up front.

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