Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_get_value

Reads the current resistance, capacitance, or inductance value of a specified RLC component by reference designator, so AI agents can inspect Multisim circuit parameters before simulation.

Instructions

读某个 RLC 元件的当前值(Ω / F / H)。

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

Input Schema

NameRequiredDescriptionDefault
refdesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses little: it does not say what happens for a non-RLC part, an invalid or unknown refdes, or a component in a closed/unsaved circuit. The one useful detail is that the returned value is expressed in Ω / F / H.

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?

A single compact sentence with the resource and the return units front-loaded and no filler. It is appropriately sized for a one-parameter getter, though it could have used the same space for one clause of usage guidance.

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 simple single-parameter getter with no output schema, stating the return units covers part of the return semantics. However, the absence of any guidance on refdes format or error cases leaves meaningful gaps for an agent that must call it correctly 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?

Schema coverage is 0% and the single parameter refdes has no title-based explanation beyond its name. The description hints that refdes identifies an RLC element, but it never states the expected format (e.g. R1, C3) or constraints, so it only marginally compensates for the coverage gap.

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 (读/read) with a specific resource (RLC 元件的当前值) and even indicates the units returned (Ω / F / H). It implicitly contrasts with the sibling msim_set_value, though it does not name it; an agent can still tell this is the read counterpart of the setter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no explicit when-to-use guidance, no prerequisites, and no direction toward alternatives such as msim_inspect or msim_list_parts for discovering valid component references. Only the implied 'read a value' usage is present.

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