Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_run_ac

Runs AC sweep frequency analysis on a Multisim circuit with probes, configuring decade, octave, or linear sweep, start/stop frequency, and point count.

Instructions

跑交流扫频分析。

sweep_type: 0=Decade 1=Octave 2=Linear start/stop: 起止频率 Hz 同样要求电路里有探针。

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_ac"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopNo
startNo
outputsNo
num_pointsNo
sweep_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the whole disclosure burden. It adds useful behavior: the sweep_type enumeration meaning and the probe prerequisite, which is a failure condition. It omits what the tool actually produces, whether results land in instruments/outputs, and whether the run blocks, which leaves real gaps for a simulation execution tool.

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?

Four short lines, front-loaded with the action and then per-parameter notes; nothing is padded. The terseness is close to the floor of what is useful rather than wasteful, though the parameter notes could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter simulation tool with no annotations, no output schema, and 0% schema coverage, the description is thin. It never explains where the swept results go, what num_points controls, or what outputs does, so an agent cannot fully predict the call's effect.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with five parameters, so the description must compensate. It does explain sweep_type (0=Decade, 1=Octave, 2=Linear) and the Hz units for start/stop, but num_points and outputs get no mention at all, leaving half the surface undocumented.

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 names a specific verb and resource: '跑交流扫频分析' (run AC sweep analysis), which is unambiguously distinct from the dc/tran siblings by domain knowledge. It does not explicitly name those alternatives, but an agent can still identify what the tool does 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies one real prerequisite, '同样要求电路里有探针' (probes must exist in the circuit), which is a genuine usage gate. However, it never states when to prefer AC over DC or transient analysis, and the alternatives are only implied by the tool name.

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