Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_disconnect_pin

Disconnects a specified pin from its net in a Multisim circuit and removes the attached wire, useful for simulating open-load conditions such as RL=∞.

Instructions

把一个引脚从它所在的网络断开(该引脚的导线一并删除)。

例如断开负载电阻的一端来模拟 RL=∞。文件层操作,保存后生效。

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": {
      "refdes": "<refdes>",
      "pin": "<pin>"
    },
    "name": "msim_disconnect_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinYes
refdesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the whole disclosure burden. It does valuable work by flagging the destructive side effect (the pin's wire is removed) and the persistence model (file-level, effective only after save). It says nothing about failure modes — what happens if the pin is already unconnected, or if the pin has multiple nets.

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?

Two compact sentences: the core action plus its side effect first, then a motivating example, then the persistence caveat. Nothing is redundant and no sentence is filler.

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?

For a two-parameter mutation tool with no annotations and no output schema, the description covers the destructive effect and save semantics well but leaves both parameter formats and any error behavior undefined. It is adequate to understand the tool but not complete enough to guarantee a correct call on the first try.

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?

Both parameters have 0% schema description coverage, so the description must compensate and does not. It never explains that 'refdes' is a reference designator nor what form 'pin' takes (number, name, or designator-qualified), which are the two things an agent most needs to fill these fields correctly.

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?

States a specific verb+resource ('把一个引脚从它所在的网络断开') and adds a non-obvious scope detail — the attached wire is deleted along with the disconnection. That distinguishes it from a mere property edit. It never names msim_connect as the inverse operation, so sibling differentiation is left implicit.

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?

Provides a concrete scenario ('断开负载电阻的一端来模拟 RL=∞') that tells the agent when this tool is the right choice, plus the workflow constraint that the change only takes effect after saving. It stops short of stating exclusions, e.g. that a still-connected pin should be handled with msim_connect instead.

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