Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_configure_instrument

Configures a Multisim function generator's frequency, amplitude, offset, and sine waveform by writing them to its SPICE model and returning before/after text for verification.

Instructions

调函数发生器面板参数:频率、幅值、偏置、波形。

amplitude 是峰值电压(与 Multisim 面板一致,不是有效值)。 waveform 目前只支持 "sine",其余波形会明确报错而不是静默忽略。 参数直接写进仪器的 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>"
    },
    "name": "msim_configure_instrument"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
refdesYes
freq_hzNo
waveformNo
amplitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does substantial work: it discloses that values are written directly into the instrument's SPICE model subcircuit, that both panel display and simulation behavior change, that unsupported waveforms raise an explicit error rather than being silently ignored, and that the before/after model text is returned. It omits permission or state requirements (e.g., whether the instrument must already be instantiated), which keeps it from a 5.

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?

Four short sentences, each front-loaded with the most important constraint first (what it configures, then the peak-voltage caveat, then the waveform restriction, then the side effects and return value). No sentence is redundant, and the semantics that matter most for correct invocation come first.

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 zero annotation coverage, no output schema, and no schema descriptions, the description covers nearly everything an agent needs: units semantics, the waveform restriction, the persistence model, and the return value. The remaining gap is the unexplained refdes parameter and the unstated requirement that the target instrument exist before configuration.

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 description coverage is 0%, so the description must supply all parameter meaning, and it supplies a lot: amplitude is explicitly peak voltage rather than RMS, waveform is constrained to "sine" with an explicit error otherwise, and the roles of freq/amplitude/offset/waveform are stated. The required refdes parameter is never explained, leaving one of five parameters undocumented in both schema and description.

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: setting the function generator's panel parameters, and it enumerates the four settings (frequency, amplitude, offset, waveform). This is clearly distinguishable from generic value-setting siblings because it targets the function generator instrument specifically. It stops short of naming any sibling tool to contrast with, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent infers it should call this when it wants to change the function generator's frequency, amplitude, offset, or waveform. There is no explicit statement of when to prefer this over a generic setter, and no mention of prerequisites such as the instrument needing to already exist in the design.

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