Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_run_dc

Runs DC operating point analysis on a Multisim circuit, using specified outputs or all probes by default; requires at least one probe to return results.

Instructions

跑直流工作点分析。

outputs 省略则跑电路里所有探针。前提:电路里必须有探针,否则没有输出。

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

Input Schema

NameRequiredDescriptionDefault
outputsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the important behavioral facts: default scope is all probes, and the run silently produces nothing if no probes exist. It omits other traits an agent would want for a simulation run — whether results are stored, how they are retrieved (e.g. via msim_get_output), and whether a prior build/save is required.

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?

Three short sentences, front-loaded with the action and followed by the default behavior and precondition; no redundant wording. It borders on under-specification rather than verbosity, but every sentence earns its place.

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

Completeness3/5

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

For a one-optional-parameter simulation trigger with no output schema and no annotations, the definition covers the essentials (what it computes, default scope, probe prerequisite). It leaves a gap around result retrieval and required circuit state, which matters because there is no output schema to explain what comes back.

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?

There is a single parameter with 0% schema description coverage and an untyped item schema ({}), so the description is the only source of meaning. It does explain that omitting outputs means all probes, which implies the array holds probe references, but it never states the expected element format (probe name, index, or object) or whether a subset restricts the returned data.

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?

"跑直流工作点分析" names a specific analysis type (DC operating point) and a clear action verb, so an agent knows exactly what computation is triggered. It does not, however, distinguish itself from the sibling analyses msim_run_ac and msim_run_tran, so the agent must infer the difference from name alone.

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?

The description supplies a real precondition (the circuit must contain probes, otherwise there is no output) and states the default when outputs is omitted. It gives no explicit guidance on when to choose this vs msim_run_ac/msim_run_tran/msim_spice_run, so alternative selection remains implicit.

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