Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_rotate_part

Rotate polarized component symbols 180° to correct diode, Zener, or LED orientation; disconnect and reconnect existing wires afterward because they do not follow the rotation.

Instructions

把元件符号旋转 180°(turns 次),电气连接点跟着转。

用于二极管/稳压管/LED 这类有极性的元件摆向不对的场合。 ⚠ 只对尚未连线或接受重连的元件使用:已画好的导线不会跟随 旋转,端点会错开,旋转后需要断开重连。

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

Input Schema

NameRequiredDescriptionDefault
turnsNo
refdesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 disclosure burden, and it handles the most important trait: existing wires do not follow the rotation, endpoints misalign, and reconnection is required. It does not state reversibility (e.g. that a second rotation restores orientation) or what response is returned, but the key side effect is clearly surfaced.

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?

Front-loaded with what the tool does, then the use case, then a warning block marked with ⚠; three short sentences with little waste. The parenthetical '180°(turns 次)' is the one awkward, ambiguity-creating fragment.

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 two-parameter tool with no output schema and no annotations, the description supplies purpose, appropriate scenario, and the critical post-condition warning. Remaining gaps are return value and the exact meaning of turns, neither of which is covered elsewhere.

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% — properties carry only titles — so the description must define both parameters. It never explains refdes, and '旋转 180°(turns 次)' is ambiguous: it is unclear whether turns is a count of 180° steps or a degree value, and no range or valid values are given for a free integer with default 1.

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?

Names a specific verb and resource (rotate the part/component symbol) plus scope (180° per turn, connection points rotate with it). No sibling tool performs rotation, so an agent can identify it immediately without opening the 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?

Gives an explicit positive case (polarized parts such as diodes, zeners, LEDs placed in the wrong orientation) and an explicit exclusion (parts already wired, unless the user accepts reconnecting). It stops short of naming the sibling workflow for the excluded case — disconnect_pin/connect are only implied by 'disconnect and reconnect after rotating'.

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