Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_save_as

Save the currently open Multisim circuit to a new .ms14 file at a specified path.

Instructions

把当前打开的电路另存为新的 .ms14。

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden and does not meet it. It does not say whether an existing file at the target path is overwritten, whether the 'currently open' circuit pointer moves to the new file (affecting subsequent msim_save), or what happens if no circuit is open.

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?

A single short sentence with the action front-loaded and no filler. It is structurally clean, but its brevity comes at the cost of the missing detail noted elsewhere rather than being genuinely complete.

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?

With no annotations and no output schema, the definition is thin for a file-writing operation. It conveys the core action adequately for a low-complexity single-parameter tool, but leaves overwrite behavior, result reporting, and path conventions unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, path, with 0% schema description coverage, so the description must compensate and does not. It never mentions the path argument, whether the .ms14 extension is required or auto-appended, or whether absolute or relative paths are accepted.

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: saving the currently open circuit as a new .ms14 file. It is clear what the tool does and is distinguishable from a plain save by the '另存为新的' (save as new) framing, though it never names msim_save as the in-place alternative.

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?

There is no guidance on when to choose this over msim_save, nor any precondition such as requiring an open circuit. The agent must infer the save-as-vs-save distinction entirely from the verb.

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