Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_export_image

Export the current circuit schematic to an image file in PNG, JPG, or BMP format for sharing or documentation.

Instructions

把当前电路原理图导出成图片。fmt: 0=png 1=jpg 2=bmp。

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

Input Schema

NameRequiredDescriptionDefault
fmtNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the operation targets the current circuit and that output format is selectable, but says nothing about whether a file at 'path' is overwritten, whether write permissions are required, whether a circuit must be open, or what is returned on success or failure. For a file-writing operation with zero annotation coverage, this is a significant gap.

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?

Two short sentences, front-loaded with the action and followed by the enum mapping. Every clause carries information and there is no filler.

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 two-parameter export tool with no output schema, the fundamentals are covered: what it does and the format values. But the meaning and constraints of the required 'path' argument, overwrite behavior, and the precondition of an open circuit are absent, leaving real gaps for an agent invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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. It does so well for 'fmt' by providing the full value mapping (0=png, 1=jpg, 2=bmp), which the schema itself lacks. However, the required 'path' parameter is never explained—whether it is a directory, a full filename, or how the extension interacts with fmt is left unclear.

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: exporting the current circuit schematic to an image file. It clearly distinguishes itself from the simulation/build siblings in the tool list. It lacks any explicit disambiguation, but no sibling performs image export, so the purpose is unambiguous.

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 is only implied by the phrase 'current circuit schematic', which suggests an active circuit must be open first. There is no explicit statement of preconditions, no when-not-to-use guidance, and no alternative tools mentioned. Given the sibling set, this is minimally adequate.

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