MCP J-Link Server

Overview Schema Source Related Servers Discussions Admin

jlink_close

Terminate J-Link debug probe connections and release all resources, including stopping RTT logging and disconnecting from target devices.

Instructions

關閉 J-Link 連線並釋放所有資源。

會自動停止 RTT（若啟動中）、斷開目標連線、關閉探針連線。

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": "jlink_close"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and effectively discloses key behavioral traits: it performs cleanup actions (closing connections, releasing resources) and automatically stops RTT if active. It covers the tool's effects well, though it could mention potential side effects like loss of debug state.

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?

The description is front-loaded with the main action ('關閉 J-Link 連線並釋放所有資源') followed by specific details in a second sentence. It is concise, with every sentence adding value, and no wasted words.

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?

Given the tool's complexity (a cleanup operation with no parameters) and the presence of an output schema, the description is mostly complete. It explains what the tool does and its automatic behaviors, but could benefit from mentioning prerequisites (e.g., requires an open connection) or confirmation of success.

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 has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description appropriately focuses on behavior without redundant parameter info, earning a baseline score of 4 for not adding unnecessary details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('關閉', '釋放') and resources ('J-Link 連線', '所有資源'), distinguishing it from siblings like jlink_open or jlink_connect. It explicitly describes what the tool does beyond just the name.

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

Usage Guidelines4/5

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

The description implies usage context by detailing what actions are performed (e.g., stopping RTT, disconnecting targets), which helps understand when to use it, such as after debugging sessions. However, it does not explicitly state when not to use it or name alternatives among siblings.

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