Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_new_circuit

Creates an empty in-memory circuit for assembling Multisim 14 designs; add parts, wire components, and place probes before saving, or build in one step.

Instructions

新建一个空电路(只在内存里,还没落盘)。

之后用 msim_add_part / msim_connect / msim_add_probe 搭电路,最后 msim_save。 也可以直接用 msim_build 一步到位。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "msim_new_circuit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well by disclosing the critical non-persistent, in-memory state. However, it does not say whether this replaces the current design or what handle/identifier is returned.

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?

Three short sentences, front-loaded with what gets created and then the next workflow steps. Every sentence adds useful information without repetition.

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 zero-parameter creation tool, the description covers the key lifecycle state and the workflow around it. The only meaningful omission is what the call returns, which would be helpful since there is no output schema.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics for the description to compensate for. The baseline for a zero-parameter definition applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: create a new empty circuit, and explicitly scopes it as in-memory and not yet saved. It also distinguishes the step-by-step path from the one-step msim_build alternative.

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

Usage Guidelines5/5

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

It explicitly says to call this first, then use msim_add_part / msim_connect / msim_add_probe and finally msim_save. It also names msim_build as the direct one-step alternative, giving the agent a clear routing decision.

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