Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_inspect

Inspect currently open circuit components, probes, variants, and simulation status to verify the design before editing or running simulations.

Instructions

查看当前已打开电路的元件、探针、变体、仿真状态。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies that the tool is read-only and notes the prerequisite that a circuit must already be open ('当前已打开电路'). However, it never explicitly confirms that this is non-destructive or that it has no side effects, which matters for an agent choosing between inspection and mutation tools.

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?

This is a single compact sentence with zero filler. The scope ('currently open circuit') and the inspected items are front-loaded, and no sentence is wasted.

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?

With no annotations, no output schema, and no parameters, the description is the only source of information an agent has. The enumeration of inspected items partly substitutes for a missing output schema, but the prerequisite 'circuit must be open' is only implied, and nothing is said about the shape or size of the result.

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?

The tool takes zero parameters, so there are no parameter semantics to explain, and the baseline is 4. The description correctly does not waste space describing an input contract that does not exist.

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 uses a specific verb ('查看' / inspect) with a clearly scoped resource set: components, probes, variants, and simulation status of the currently open circuit. This is more informative than a bare restatement of the name 'msim_inspect'. However, it does not distinguish itself from nearby siblings such as msim_status or msim_list_parts, which likely overlap with parts of this inspection.

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

Usage Guidelines2/5

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

The description states what is inspected but gives no when-to-use guidance, no exclusions, and no named alternatives. There is no pointer to msim_status or msim_list_parts when only a subset of the state is needed, so the agent must infer the right choice from tool names alone.

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