Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_get_output

Retrieves waveform data from a named probe after a Multisim analysis finishes and returns x-y points for DC, AC, or transient results.

Instructions

读取一个探针的波形数据(分析跑完之后调)。

返回 points = [[x, y], ...]。DC 分析通常只有 1 个点。

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": {
      "name": "<name>"
    },
    "name": "msim_get_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
max_pointsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 burden. It does disclose the return shape ([[x, y], ...]) and the DC corner case of a single point, which is real added value, but it is silent on what max_points does to the result, whether points are truncated or downsampled, and what happens if the probe name is unknown.

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, front-loaded with the action and the timing precondition, followed by the return format and the DC caveat. Nothing is padded and every line adds information.

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?

Adequate for a simple read-only getter with only two parameters, and the return-value note compensates for the absent output schema. It is still incomplete on truncation semantics and error behavior for an invalid probe name, which matter because max_points silently shapes the payload.

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%, so the description must compensate, and it only half does: 'reads one probe's waveform data' implies that name is the probe identifier, but max_points (default 2000) is never explained even though it directly governs the output the description spends a line describing.

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?

A specific verb and resource: reads one probe's waveform data, with the post-analysis timing condition parenthesized. It contrasts implicitly with a single-value getter, but never names msim_get_value as the scalar alternative, so differentiation from siblings is only partial.

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?

'Call after the analysis has run' is a genuine precondition and the most useful usage signal here. There are no exclusions or named alternatives, however, so an agent must still infer from sibling names whether this or msim_get_value / msim_inspect is right.

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