Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_connect

Connects component pins into a named net and automatically draws the wires, optionally placing a voltage probe so simulation analyses can read waveforms.

Instructions

把若干引脚连成一条网络(自动画导线)。

net 网络名,如 "out"。地网统一写 "0"("gnd"/"ground" 会自动归一化) pins 引脚引用列表,格式 "元件.引脚名",如 "R1.1"、"Q1.B"、"Q1.C"、"Q1.E"。 注意三极管引脚名是字母 C/B/E,不是数字,写错会直接报错 probe 是否在这条网络上放一个电压探针(有探针才能跑分析读波形) probe_at [x, y] 探针落点;必须落在该网络的水平导线段上, 省略则在最长水平段中点自动插点。给了非法坐标会报错而不是静默失效

一个引脚只能属于一条网络,重复连接会报 PIN_CONFLICT。 地网需要多段时,重复调用本函数、net 都写 "0" 即可。

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": {
      "net": "<net>",
      "pins": "<pins>"
    },
    "name": "msim_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
netYes
pinsYes
probeNo
probe_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does most of that work: it discloses that the tool mutates the design by adding wires, that a pin already owned by a net raises PIN_CONFLICT, and that invalid probe_at coordinates error rather than silently failing. It does not state the return value or whether the connection can be undone, which leaves a small 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?

Front-loaded with the one-line purpose, then per-parameter lines in the order of the schema, with the risky details (transistor pin naming, probe placement legality) bolded where they matter. Slightly dense but no sentence 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 four-parameter mutating tool with no annotations and no output schema, the definition covers parameter formats, error behavior, and the net-membership invariant. It is only missing preconditions (open circuit/edit mode, as implied by siblings like msim_open and msim_edit_open) and a note on what a successful call returns.

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?

With 0% schema description coverage, the description compensates fully: net (with ground-normalization semantics), pins ("元件.引脚名" format with R1.1 and Q1.B/C/E examples plus the explicit warning that transistor pins use C/B/E, not numbers), probe (only with a probe can analyses read waveforms), and probe_at (must land on a horizontal wire segment, defaults to the midpoint of the longest horizontal segment). Each of the four undocumented parameters now has real meaning.

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 states a specific verb and resource: "把若干引脚连成一条网络(自动画导线)" – joining pins into a net with automatic wire drawing. That is enough to distinguish it from disconnect_pin or delete_part, but it never contrasts itself with the probe-related siblings (msim_add_probe) even though the optional probe/probe_at arguments overlap with them.

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 gives useful in-context rules: ground nets must be written as "0" (gnd/ground are normalized), one pin can only belong to one net, and repeat calls are the way to make several ground segments. However, it says nothing about prerequisites (must a circuit be open/edit mode entered first?) or when an agent should use it instead of the sibling probe-placement tool.

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