Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_list_instruments

Lists virtual instruments available for placement in Multisim circuits—oscilloscope, multimeter, function generator, and pin names—and can include custom instruments from a donor .ms14 file.

Instructions

列出可放进电路的虚拟仪器:示波器、万用表、函数发生器,以及引脚名。

kind 直接传给 msim_add_instrument。传 donor(一个 .ms14 文件)可额外列出 该设计里所有 X 开头的仪器,用来接波特图仪、逻辑分析仪等自定义仪器。

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

Input Schema

NameRequiredDescriptionDefault
donorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the non-obvious behavior: with donor the tool reads an external .ms14 design file and enumerates its X-prefixed instruments, rather than just returning the built-in list. It does not cover failure behavior for an invalid or missing donor path, which is the remaining gap.

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 lines: what is listed, what to do with the output, then the optional donor mode. The progression is front-loaded and every sentence adds new 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?

With no output schema and a single optional parameter, the description covers the returned contents, the downstream usage, and the donor variant well enough to call it correctly. Only the return shape and error conditions are left implicit.

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?

Schema coverage is 0%, so the description must supply all meaning, and it does explain donor as a .ms14 file plus its effect, and clarifies that kind is a return value to be passed to msim_add_instrument rather than an input. Format details for the donor path (relative vs absolute, error handling) are still unstated.

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+resource ('列出可放进电路的虚拟仪器') and enumerates the returned categories (oscilloscope, multimeter, function generator, pin names), which clearly separates it from msim_list_parts. It also names the downstream consumer, msim_add_instrument, so an agent knows exactly where this tool sits in the workflow.

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 states the condition that selects the optional donor mode: pass a .ms14 file when you need X-prefixed custom instruments such as a Bode plotter or logic analyzer. It implies the default call path (list, then feed kind to msim_add_instrument), but gives no explicit exclusion or note about when not to use it.

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