MCP J-Link Server

Overview Schema Source Related Servers Discussions Admin

jlink_erase_chip

Erase the entire Flash memory of a target chip using the MCP J-Link Server. This irreversible action clears all programmed firmware from the device.

Instructions

擦除目標晶片的整個 Flash 記憶體。

注意：此操作不可逆轉，將清除晶片上所有已燒錄的韌體。

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

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.7/5.0

Behavior5/5

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

With no annotations provided, the description carries full burden and does an excellent job. It explicitly warns that the operation is irreversible ('不可逆轉') and will clear all firmware ('清除晶片上所有已燒錄的韌體'), which are critical behavioral disclosures for a destructive operation.

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 sentences with zero waste. The first states the purpose, the second provides critical warning. Both sentences earn their place by adding essential information beyond what's in the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, zero-parameter tool with no annotations but with an output schema, the description is complete. It explains what the tool does, its irreversible nature, and the scope of destruction. The output schema will handle return values.

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 the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the operation's implications.

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 specific action ('擦除' - erase) and target resource ('目標晶片的整個 Flash 記憶體' - entire Flash memory of target chip). It distinguishes from siblings like jlink_flash_file (which writes) and jlink_memory_write (which writes specific addresses).

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 provides clear context about when to use this tool - for erasing the entire chip's Flash memory. However, it doesn't explicitly mention when NOT to use it or name specific alternatives like jlink_memory_write for partial erasure.

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