Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_read_design

Reads a saved Multisim .ms14 file to extract components, pins, nets, and probe counts, so agents can inspect the latest circuit after a manual save when COM access is unavailable.

Instructions

读取一个 .ms14 的完整结构:元件、引脚、网络、探针数(纯文件层)。

典型用途:你在前台 Multisim 里 Ctrl+S 保存后,agent 用它读取你的 最新电路。Multisim 的 COM 接口无法连接到第三方启动的 GUI 实例 (实测无 ROT 注册),所以「前台协作」的唯一可靠通道就是文件: 你保存 → agent 读这个文件 → agent 产出新文件供你打开。 原件不会被修改。

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

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 supplied, the description carries the full burden and does well: it declares the operation is non-destructive ('原件不会被修改'), that it operates on the file layer rather than a live instance, and that the save-then-read-then-produce-a-new-file round trip is the intended workflow. It does not describe behavior on a missing, corrupt, or locked file, which is the remaining gap for a file-reading 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?

The purpose and return contents are front-loaded in the first line, followed by the scenario and rationale. The COM/ROT explanation is longer than strictly necessary but is the justification an agent needs to choose this over a live-instance tool, so it earns its place.

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?

There is no output schema, and the description compensates by enumerating the returned structure (components, pins, nets, probe count). For a single-parameter read tool with no annotations, the only material omission is path formatting and failure behavior.

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 coverage is 0% for the single 'path' parameter, so the description must compensate; it establishes the file is a .ms14 design file but never says whether the path must be absolute, relative to a workspace, or whether the extension is required. The extension hint adds some meaning beyond the bare schema, but not full semantics.

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 gives a specific verb plus resource (read a .ms14 file's full structure) and enumerates exactly what is returned: components, pins, nets, probe count. The parenthetical 'pure file layer' distinguishes it from the COM-backed siblings like msim_open or msim_inspect, though no sibling is named explicitly.

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?

It states the concrete usage scenario ('after you Ctrl+S in foreground Multisim, the agent reads your latest circuit') and explains why this channel exists: the COM interface cannot attach to a third-party GUI instance with no ROT registration. That effectively defines when to use this instead of a live-GUI tool, but no alternative tool name is offered for contrast.

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