Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_run_tran

Run transient analysis to capture time-domain circuit waveforms and retrieve time-voltage data points for simulation results.

Instructions

跑瞬态分析,用来拿波形(相当于示波器看到的曲线)。

duration 仿真时长(秒),默认 3ms(3 个 1kHz 周期) sample_rate 采样率(Hz),默认 200kHz output 探针名,省略则用第一个探针

跑完用 msim_get_output 读数据,points 里是 [时间, 电压] 的点列。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "msim_run_tran"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNo
durationNo
sample_rateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so the description carries full burden. It discloses that the run yields waveform point data shaped as [时间, 电压] and that a probe must exist, but says nothing about runtime, blocking behavior, whether prior results are overwritten, or what happens if no probe is defined.

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 one-line purpose followed by an aligned parameter block and a next-step line. Compact and scannable; only the parenthetical analogy is arguably decorative.

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 simulation tool with no output schema, it covers units, defaults, return data shape, and the follow-up read step. The gap is error/precondition handling and the choice relative to the AC/DC siblings.

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%, yet the description documents all three parameters with units, defaults, and rationale: duration in seconds with default 3ms explained as three 1kHz periods, sample_rate in Hz defaulting to 200kHz, and output as a probe name defaulting to the first probe. This fully compensates for the empty 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?

States a specific verb and resource ('跑瞬态分析') and adds an analogy that pins down the output type ('相当于示波器看到的曲线'). The qualifier '瞬态' distinguishes it from the AC/DC siblings, though those siblings are never named.

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?

Gives a clear post-run step ('跑完用 msim_get_output 读数据'), which implies the tool is a producer of data consumed elsewhere. It never says when to choose transient over AC or DC analysis, or what preconditions (netlist built, probes placed) must hold.

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