Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_add_instrument

Adds a virtual oscilloscope, multimeter, or function generator to the current Multisim circuit, with optional reference designator placement and donor-based instrument copying.

Instructions

在当前电路里放一台虚拟仪器。

kind "oscilloscope" / "multimeter" / "function_generator", 也接受 scope、meter、fgen、XSC、XMM、XFG 等别名 refdes 位号,省略则自动取下一个空位(XSC1、XSC2…) x, y 面板在图纸上的位置 donor, donor_refdes 可选:从任意 .ms14 里复制任意仪器(配合 msim_list_instruments(donor=...))

仪器引脚像普通元件一样可以写进 msim_connect 的 pins 列表。 COM 的 EnumOutputs 只认探针,所以仪器负责图和连线,读数仍用 msim_connect(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": {
      "kind": "<kind>"
    },
    "name": "msim_add_instrument"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
kindYes
donorNo
refdesNo
donor_refdesNo

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?

No annotations exist, so the description carries the full burden and does a fair job: it discloses auto-assignment of the next free refdes (XSC1, XSC2…), that instrument pins are connectable like any component, and the important limitation that COM's EnumOutputs only sees probes, not instruments. It omits error behavior, persistence/undo semantics, and what is returned 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?

One-line purpose followed by a front-loaded, scannable parameter glossary and a short integration note; nearly every sentence carries information. Slight redundancy between the donor entry and the trailing paragraph, and the mixed-language body requires the agent to parse two contexts.

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 6-parameter mutation tool with no annotations and no output schema, the description covers inputs, the donor workflow, and the probe/instrument division of labor well enough to invoke it correctly. Remaining gaps (failure modes, return payload, whether changes are immediate vs saved) are minor given tool complexity.

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% and has no enums, yet the description defines all meaningful parameters: kind with three canonical values plus alias list (scope, meter, fgen, XSC, XMM, XFG), refdes auto-allocation behavior, x/y as schematic panel position, and donor/donor_refdes as a paired copy-from-.ms14 mechanism. This is exactly the compensation the schema lacks.

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?

States a concrete verb + resource ('放一台虚拟仪器' = place a virtual instrument in the current circuit) and implicitly separates itself from msim_add_part by noting that instrument pins behave like normal component pins. The named sibling tools (msim_connect, msim_list_instruments) make the boundary concrete.

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?

Gives a clear contextual rule for the optional donor path ('配合 msim_list_instruments(donor=...)'), and closes with the workflow constraint that readings must come from probes added via msim_connect(probe=True). It does not give an explicit when-not (e.g. when to use msim_add_part instead), but the operating context is clear.

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