Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_save

Save the current Multisim 14 circuit as a .ms14 file; the .ms14 extension is required for COM automation to reopen it.

Instructions

把当前电路写成 .ms14 文件(必须 .ms14 后缀,否则 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_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 disclosure burden. It does add one genuinely valuable behavioral constraint, namely that the .ms14 extension is mandatory because the COM layer cannot open other names, but it says nothing about overwriting an existing file, error behavior, or whether a circuit must be loaded first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that leads with the action and immediately follows with the hard constraint. Nothing is redundant, and the most failure-prone detail is placed where an agent will see it first.

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 write operation with no annotations and no output schema, the description covers the essential pitfall: a wrong file name extension. It is thin on overwrite semantics and the save-versus-save-as relationship, but it is largely sufficient for calling the tool correctly.

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%, so the schema offers the agent nothing beyond a string named path. The description partially compensates by imposing the .ms14 suffix requirement, but it does not clarify whether the value is a full file path or a directory, or whether relative paths are resolved against a working directory.

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 writes the current circuit to a .ms14 file. The core operation is unambiguous, but it never distinguishes itself from the sibling msim_save_as, leaving the save-versus-save-as boundary to inference.

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?

Usage is only implied: an agent can infer you call this to persist the current circuit. There is no explicit statement of when to use it instead of msim_save_as, nor any precondition such as a circuit already being open.

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