keil-mdk-mcp

by lideshengstu

Overview Schema Source Related Servers Discussions Admin

Python

Local

keil_reset

Reset an MCU only after explicit human authorization via confirm=true, with an option to halt the core afterward.

Instructions

Reset MCU only after human-authorized confirm=true; optionally halt afterward.

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

Input Schema

Name	Required	Description	Default
`confirm`	No
`halt_after`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 3, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description usefully discloses the human-authorization gate and the possibility of halting after the reset. It does not state whether confirm=false causes rejection or a no-op, nor does it clarify effects on execution or the debug session.

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 single sentence is front-loaded with the action and immediately follows it with the safety precondition and optional behavior. There is no filler or repetition.

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?

For a simple two-parameter operation with an output schema and defaults in the input schema, the description covers the main action, invocation guard, and optional follow-up behavior. Remaining ambiguity around unauthorized calls and debug-session effects prevents a top score.

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?

Although schema description coverage is 0%, the description gives practical meaning to both booleans: confirm must be true after human authorization, and halt_after is reflected by "optionally halt afterward." It leaves unauthorized-call behavior and the non-halting post-reset state implicit.

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 phrase "Reset MCU" supplies a specific verb and resource, while "optionally halt afterward" clarifies the immediate outcome. It does not explicitly distinguish the operation from siblings such as keil_halt or keil_stop_debug.

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?

"Only after human-authorized confirm=true" provides a concrete precondition and an implicit when-not-to-invoke rule. It does not describe typical reset scenarios or direct the agent to alternatives when a halt or debug-session restart would be more appropriate.

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