Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_delete_part

Remove a component and all associated pins, model, symbol, and wiring from the current Multisim design so the build session reflects the deletion before saving or simulation.

Instructions

把一个元件从当前设计里整体移除(引脚、模型、符号、相关导线一起清)。

文件层操作:改的是构建会话,之后 msim_save 保存、msim_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": {
      "refdes": "<refdes>"
    },
    "name": "msim_delete_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
refdesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the destructive blast radius (pins, model, symbol, related wires all removed together), that the change lands in the build session and only persists via msim_save, and that outputs from deleted probes/instruments vanish with it. It omits reversibility/undo behavior and what happens when the refdes is not found.

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?

Three short lines, front-loaded with the core action before the file-layer caveat and the side-effect note. Minor deduction for an awkward line break mid-clause ('才进入 / 仿真通道') that slightly impedes reading, but no sentence is padding.

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 one-parameter delete with no output schema and no annotations, the definition covers what is destroyed, which session it affects, and the follow-up save requirement — enough to call it safely. The remaining gap is error/return behavior and refdes semantics, which is minor for a tool this simple.

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 description coverage is 0%, so the description would ideally explain the single 'refdes' argument, but it never mentions it — it only says '一个元件'. The parameter name is largely self-describing, which keeps this from being a 2, but no format, validation, or lookup guidance is added beyond the schema.

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 states a specific verb and resource — '把一个元件从当前设计里整体移除' — and immediately scopes it with '(引脚、模型、符号、相关导线一起清)'. That scope detail distinguishes it from a pin-level operation like msim_disconnect_pin and from the inverse msim_add_part without needing to open any schema.

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 clearly frames when this applies: '文件层操作:改的是构建会话,之后 msim_save 保存、msim_open 才进入仿真通道' tells the agent this belongs to the build/session phase rather than the simulation phase, and that a save is needed to persist. It stops short of naming an explicit alternative for the narrower case (e.g., detaching a single connection), so no exclusion rule is given.

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