Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_set_model

Updates a BJT or diode component’s displayed model name and SPICE parameters while preserving its internal .MODEL key so Multisim symbols and attributes stay synchronized.

Instructions

换元件的显示型号与模型参数(BJT/二极管换型号用)。

model_name 新显示型号,如 "2N3904"(图上标注和属性同步替换) model_text 新模型参数体,如 "NPN IS=6.734E-15 BF=416.4 ..."; 省略则只换显示名

注意:内部 .MODEL 键保留原名不改(改了会与 Multisim 元件数据库 失绑,文件打开即崩——实测),所以仿真参数换、网表 .MODEL 名不变, 对仿真结果无影响。同步 SPICE 参数体、属性槽、符号显示文字, 返回替换后的模型文本。

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>",
      "model_name": "<model_name>"
    },
    "name": "msim_set_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
refdesYes
model_nameYes
model_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 so well: it discloses that SPICE parameter body, property slots and symbol display text are all updated synchronously, that the internal .MODEL key is deliberately left unchanged (with a concrete crash consequence), and that the replaced model text is returned. It omits prerequisites (design must be open, refdes must exist) and error behavior for invalid model text.

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 purpose sentence, then parameter notes, then the important caveat — a logical order with little waste. The .MODEL-key warning is long but earns its place because it prevents a destructive mistake.

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-parameter mutation tool with no annotations and no output schema, the description covers mutation targets, invariants, side effects and the return value. What is missing is only the surrounding workflow state (open design, valid refdes) and failure modes.

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

Parameters4/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 explains two of three parameters with concrete examples and a default semantic for model_text omission. refdes is left undefined, presumably assumed obvious to a SPICE/EDA-savvy agent, which is the only real gap.

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 opening sentence gives a specific verb (set/replace) and a precise resource (display model name + model parameter body), and scopes it to BJT/diode model changes. An agent can tell this apart from value-editing siblings without opening the 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?

The parenthetical 'BJT/二极管换型号用' states the situation in which to reach for this tool, and the model_text default ('omitted means only change the display name') clarifies a common usage mode. It stops short of naming an alternative sibling such as msim_set_value or stating when not to use it.

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