Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_add_probe

Adds a voltage probe to an existing net so DC and transient simulations can read node values, including orphaned nets after pin removal or nodes in edited designs.

Instructions

给一个已经存在的网络补电压探针(之后 run_dc/run_tran 可读它)。

适合两种场合:msim_disconnect_pin 摘掉引脚后探针变孤儿的网; 或者编辑既有设计(msim_edit_open)后想读某个节点的值。

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": {
      "net": "<net>"
    },
    "name": "msim_add_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
netYes

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 at all, the description carries the full burden. It usefully discloses that the probe becomes readable by later run_dc/run_tran calls and that the target must be an existing net, but it says nothing about failure behavior for a nonexistent or duplicate net, or whether the design is mutated or must be saved afterward.

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?

The purpose is front-loaded in the first line, followed by the two usage scenarios. Both sentences carry information and nothing is padded, though the parenthetical asides make it slightly less crisp than it could be.

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 one-parameter mutation tool with no annotations and no output schema, the description covers the essential purpose and consumers but leaves out error conditions, idempotency, and whether the probe persists in the saved design. Adequate but with clear gaps.

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 coverage is 0% for the single 'net' parameter, so the description must compensate. It does convey that the value is a net name and must already exist, which is more than the bare schema says, but it gives no naming format, path syntax, or hierarchy conventions.

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 pairs a specific verb and resource ('add a voltage probe to an existing net') and states the downstream consumers (run_dc/run_tran can read it), so the agent knows exactly what the tool creates. It stops short of explicitly distinguishing itself from other creation tools such as msim_add_instrument, which keeps it from a 5.

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?

It names two concrete occasions for use: orphaned nets left after msim_disconnect_pin, and reading a node value after msim_edit_open. That is clear contextual guidance, but there is no explicit 'do not use when' or a stated alternative for other probe scenarios.

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