Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_add_part

Places a component in the current Multisim circuit by refdes and kind, optionally setting value and coordinates, then returns its pins for wiring.

Instructions

往当前电路里放一个元件。

refdes 位号,如 "R1"、"V1"(同一电路内必须唯一) kind 元件种类,见 msim_list_parts,如 "resistor"、"dc_source"、"ground" value 主参数(电阻 Ω、电容 F、电感 H、电源 V)。ground 不需要 x, y 放置坐标(Multisim 图纸单位,栅格 9)。省略则自动布局

返回该元件的引脚列表,供 msim_connect 使用。

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": {
      "refdes": "<refdes>",
      "kind": "<kind>"
    },
    "name": "msim_add_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
kindYes
valueNo
refdesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 behavioral burden. It does disclose key behavior: refdes must be unique within the circuit, x/y are optional and default to auto-layout, ground needs no value, and the call returns pin data for wiring — but it never states what happens on a duplicate refdes (error vs. rename), whether placement fails outside a grid or without an open circuit, or whether the add is undoable.

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?

One scope sentence followed by a compact per-parameter list where each line adds distinct information, with the return-value note last. Nothing is redundant and the tool's identity is front-loaded.

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 five-parameter mutation tool with no annotations and no output schema, most of what an agent needs is present, including the return shape (pin list). The remaining gap is failure/chaining behavior: duplicate-refdes handling and the requirement of an active circuit are unstated.

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 description coverage is 0% and the description fully compensates: refdes semantics (unique per circuit), kind with a lookup pointer and examples, value with per-kind units (Ω/F/H/V) and the ground exemption, and x/y with the drawing-unit/grid-9 convention plus auto-layout default. All five parameters gain meaning not present in the bare schema.

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 opening sentence gives a concrete verb+resource: place a component into the current circuit, and the kind enumeration (resistor, dc_source, ground) makes clear this is a schematic-element tool, not an instrument/measurement tool. It does not name a sibling it is explicitly not (e.g. msim_add_instrument), so differentiation is real but implicit rather than stated.

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 clear workflow context: kinds should be looked up via msim_list_parts, and the returned pin list is meant for msim_connect. There are no explicit exclusions or preconditions (e.g. requires an open circuit via msim_new_circuit/msim_open), so an agent still has to infer the entry conditions.

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