Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_status

Checks whether the 32-bit worker is available, Multisim COM is connected, and the current circuit state before any operation, without opening a visible Multisim window.

Instructions

查询当前环境:32 位 worker 是否可用、Multisim COM 是否连得上、当前电路状态。

这是任何操作前应该先调的工具。不启动 Multisim 的可见窗口。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

There are no annotations, so the description must disclose behavior on its own. It does disclose a key trait: it will not start a visible Multisim window, which prevents the agent from misreading the call as a launch action. However, it does not clarify whether COM is initialized or started as a side effect, or whether any state changes, leaving real ambiguity for a zero-parameter diagnostic.

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?

It is three short sentences: the first lists what is checked, the second sets the call ordering, the third sets a constraint. The constraint and ordering both come before any explanation, and no sentence restates the tool name redundantly.

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?

It is a zero-parameter, no-annotation tool with no output schema, so the description must define the result surface, and it does by enumerating the three statuses returned. It stops short of stating result format (booleans vs. structured status objects) or what to do if COM is unavailable, leaving a small but real gap.

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 it has no parameter semantics to explain; the baseline for that case is 4. The description instead spends its text on what the fixed output categories are, which is the right use of space for a no-arg tool.

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 uses a specific verb and resource ('查询当前环境' / query current environment) and then names exactly what it reports: 32-bit worker availability, Multisim COM connectivity, and current circuit state. It also distinguishes itself from msim_open by stating it does not launch a visible Multisim window, which prompts the agent to choose this diagnostic rather than the launch tool.

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?

The description gives explicit routing guidance with '这是任何操作前应该先调的工具' (this is the tool to call first before any operation), which is a clear precondition for the sibling tools msim_open/msim_build/msim_run_*. It lacks any when-not or condition where its results can be skipped, so it falls short of the full when/when-not/alternatives pattern.

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