Skip to main content
Glama
multisim-mcp

multisim-mcp

by Aruvelut111

msim_close

Close hidden Multisim instances and release resources by terminating the worker process.

Instructions

关闭隐藏的 Multisim 实例,释放资源(直接结束 worker 进程)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure burden. It does add genuinely useful behavior by revealing the mechanism is a forced worker-process kill ('直接结束 worker 进程'), which signals that in-flight state may be lost. It does not state whether unsaved design changes are discarded, whether the call is idempotent when no instance exists, or whether the worker restarts.

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?

A single front-loaded sentence with the action first and the consequence in parentheses; nothing is padded or repeated. The parenthetical is the highest-value clause and is placed where it will be read.

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 behavioral evidence an agent has. It covers the mechanism but omits the consequences an agent needs before forcefully killing a process — loss of unsaved work, behavior when no instance is running, and any post-close state.

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 is no parameter meaning to document and the baseline of 4 applies. Nothing in the description misrepresents or omits an argument.

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?

States a specific verb and resource ('关闭隐藏的 Multisim 实例' — close the hidden Multisim instance) plus the resource-release intent, which clearly separates it from lifecycle siblings such as msim_open and msim_edit_open. It stops short of naming an alternative explicitly, so it lands at 4 rather than 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 is only implied: the phrase '释放资源' (release resources) suggests a teardown/cleanup role, but the definition never says when to call it versus leaving the instance running, nor whether it should follow msim_save or msim_get_output. No exclusions or prerequisites are given.

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