Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_set_value

Update an RLC component's value—resistance (Ω), capacitance (F), or inductance (H)—by reference designator to change circuit behavior before simulation or saving.

Instructions

改某个 RLC 元件的值(Ω / F / H),改完可以用 msim_save_as 存盘。

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>",
      "value": "<value>"
    },
    "name": "msim_set_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
refdesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose one real behavioral trait — the edit is not persisted unless msim_save_as is called — which is genuinely beyond what structured fields provide. It says nothing about error behavior for an unknown refdes, whether the change takes effect immediately, or whether a rebuild/rerun is required.

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 action and units front-loaded and the follow-up save hint trailing. No wasted words, though the brevity edges toward under-specification rather than optimal density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with zero annotation coverage and no output schema, the definition omits prerequisites (active circuit/design), refdes semantics, and what happens on invalid input. The save hint is the only piece of operational context provided.

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 description coverage is 0% for both parameters. The description partially compensates for 'value' by giving acceptable units, but 'refdes' is never explained (reference designator of the target component, format, or how to discover valid ones via msim_list_parts).

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?

States a specific verb and resource: change the value of an RLC element, with units (Ω / F / H) clarifying the value domain. This distinguishes it adequately from msim_get_value (read) and msim_set_model (model-level rather than value-level), though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

The only guidance is a workflow hint that changes can be persisted via msim_save_as, which usefully implies the edit is in-memory until saved. There is no statement of when to prefer this over msim_set_model, nor any precondition such as requiring an open/active circuit.

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