Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_open

Opens a Multisim .ms14 file in a fresh hidden instance and returns its components and probe list, retrying automatically on transient COM access errors.

Instructions

用 Multisim(隐藏实例)打开一个 .ms14,返回元件和探针列表。

每次打开都换全新 worker + 全新 Multisim 实例(复用会因多文档状态残留 让 EnumOutputs 交替返回 None)。上一个实例偶发还没退干净就连上去, COM 会抛「拒绝访问」——这种瞬时错误自动换实例重试一次。

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": {
      "path": "<path>"
    },
    "name": "msim_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose real behavior (a brand-new worker and Multisim instance per open, the EnumOutputs state-residue rationale, and one automatic retry on transient COM 'access denied'). However it omits whether the opened file is ever modified, whether the hidden instance persists until msim_close, permission/auth requirements, and any timeout expectation, so significant gaps remain for a mutating lifecycle 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?

Purpose is front-loaded in the first sentence, with behavioral caveats in a compact follow-up; the parenthetical explanations of why a fresh instance is required earn their space. The composition is dense but not padded.

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?

With one required parameter and no output schema, the description covers the return payload ('元件和探针列表') and the retry/error behavior, which is more than most definitions this simple offer. The remaining hole is lifecycle: nothing says the hidden worker must be released via msim_close, which an agent needs to avoid leaking instances.

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% for the single 'path' parameter, so the description must compensate. It adds that the path points to a .ms14 file, which is the key semantic constraint, but gives no guidance on absolute vs relative paths, whether the file must exist or be closed, or accepted path forms.

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 ('用 Multisim(隐藏实例)打开一个 .ms14') plus the return content ('返回元件和探针列表'), which is concrete and actionable. It never differentiates itself from the close sibling msim_edit_open or from msim_new_circuit, so an agent cannot tell from the text alone which open variant to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only usage signal is implicit: '隐藏实例' suggests headless inspection rather than interactive editing. There is no explicit when-to-use, no when-not-to-use, no mention of msim_edit_open as the alternative, and no stated prerequisite such as needing a subsequent msim_close call to release the hidden instance.

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