Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_list_parts

Lists available component kinds and sample-library parts to check valid options before building a circuit, preventing errors from using nonexistent kinds.

Instructions

列出可用的元件种类(kind 字符串)以及样例库里实际存在的库元件。

搭电路前先看这个,避免用了不存在的 kind。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It conveys what the listing contains and implies a safe read-only lookup, but it does not state the result shape (flat list vs. grouped by category), ordering, or whether the catalogue is static or reflects the current sample library state.

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 short sentences: the first states the return contents, the second states the usage rule and its motivation. Nothing is redundant and the content is front-loaded.

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 parameterless discovery tool with no output schema, the description covers both purpose and return contents at a high level. It stops short of describing the output structure, which is the one thing an agent would still have to discover by calling it.

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 there is no parameter meaning to document and the baseline applies. The description correctly does not invent inputs; the only relevant semantics, that output kinds are the `kind` strings accepted elsewhere, is mentioned.

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 names a specific verb and two concrete resources: the set of available part kinds (as `kind` strings) and the library parts that actually exist in the sample library. That is enough for an agent to distinguish it from mutation siblings like msim_add_part or msim_delete_part, though it does not explicitly contrast itself with msim_list_instruments.

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 gives an explicit when-to-use rule — call this before building a circuit — along with the reason (avoid referencing a non-existent kind). There are no explicit exclusions or named alternatives, but for a discovery tool the guidance is actionable.

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