Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_edit_open

Loads an existing Multisim 14 (.ms14) file into an edit session so subsequent tools can modify components, wires, values, and models, then save changes to a new file.

Instructions

把一个已有的 .ms14 装进编辑会话,之后所有编辑工具对它生效。

典型用途:用户前台 Multisim 里 Ctrl+S 保存后,agent 用 msim_read_design 看结构,再用本工具装进会话做修改(删元件、断线、改值、换模型……), 最后 msim_save_as 存成新文件(原文件不会被覆盖,除非显式指到原路径)。

会话里的元件/网络缓存会从文件重建;已有探针的位置关联比较复杂, 不做重建——编辑会话里再放探针可能与既有探针重复,需要探针时优先 用 msim_add_probe 按网络名补。

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

Input Schema

NameRequiredDescriptionDefault
pathYes

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 covering safety or side effects, the description carries the full burden and mostly meets it: it says the source file is not overwritten unless the caller explicitly targets the original path, that component and net caches are rebuilt from the file, and that existing probe associations are deliberately not rebuilt because duplicates may appear. It leaves open how session lifecycle works, for example whether a second call replaces an existing session or creates another one.

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?

The key statement is front-loaded in the first line, and later sentences carry real information rather than noise. The probe paragraph is a genuine caveat, but it is somewhat tangential to the act of opening a session and could be tighter; overall the structure remains readable despite the multi-line layout.

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 one-parameter mutation-state tool with no annotations, no output schema, and no rate-limit metadata, the description covers workflow placement, persistence behavior, cache rebuild semantics, and probe caveats. Missing pieces are error and return behavior, plus session-lifecycle rules, which matter for an agent deciding whether calling it twice is safe.

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 one required parameter, 'path', and the schema description coverage is 0%, so the description must compensate. It conveys that the path must point to an existing .ms14 file and hints at path-based behavior when talking about explicitly targeting the original path. However, it never states whether the path must be absolute, how relative paths are resolved, or what happens when the file is missing or already open.

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: it loads an existing .ms14 file into an edit session so that all subsequent editing tools apply to that file. It also implicitly distinguishes the tool from msim_read_design (read-only structure inspection) and msim_save_as (persisting). It never explicitly contrasts with the sibling msim_open, so a reader must infer how this tool differs from simply opening a file.

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

Usage Guidelines4/5

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

A concrete workflow is spelled out: after the user saves in Multisim, call msim_read_design to inspect the structure, then call this tool to make the design editable, then call msim_save_as to write a new file. It also says when to prefer msim_add_probe instead of preserving probes. It omits explicit when-not-to-use conditions, such as whether to use msim_open for read-only inspection.

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