Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_report_bom

Generates a bill of materials from a Multisim 14 design, listing reference designators, part numbers, and schematic values; reads the active session or a specified .ms14 file without modifying it.

Instructions

元件清单(BOM):位号、型号、图面标注值。

path 省略时读当前编辑会话;给了路径则直接读那个 .ms14(原件不动)。

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does earn credit for disclosing that a given path reads the file directly and that the original is left unmodified (non-destructive read), but it says nothing about error behavior (e.g., missing/invalid path), whether reading a large design is slow, or the shape of the returned report beyond naming three fields.

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?

Two sentences: the returned fields are front-loaded, followed by the parameter branch. There is no filler, and the important behavioral caveat (原件不动) is attached to the branch it modifies. Slightly denser phrasing could merge the label-style first clause, but nothing is wasted.

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 one-optional-parameter read tool with no output schema, the definition covers the essentials: what is returned, where it reads from, and that the source file is not mutated. The main residual gap is the exact report structure and failure handling for a bad path, which is minor for a tool of this complexity.

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?

Schema coverage is 0%, so the description must compensate, and it does: the single 'path' parameter is explained with both branches — omitted means current editing session, provided means read that specific .ms14 file. That meaning is not derivable from the bare schema (a nullable string with default null), though it doesn't state accepted path formats or file extensions beyond .ms14.

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 states a specific verb and resource and enumerates exactly what the report contains (位号/reference designators, 型号/part type, 图面标注值/drawing annotation values). An agent knows this produces a BOM listing rather than an edit. It does not explicitly distinguish itself from siblings like msim_list_parts or msim_read_design, which keeps it off a 5.

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?

Usage context is only implied through the path branches: omit path to read the current editing session, supply a path to read a .ms14 file. There is no when-to-use vs when-not-to-use framing and no routing to the plausibly overlapping siblings such as msim_list_parts or msim_read_design, so the agent must infer which reporting tool to pick.

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