MCP server for Keil µVision embedded development environment, providing tools to connect to and control Keil µVision debugger via UVSC (UVSOCK Client) DLL interface
18 tools with consistent naming (verb_noun pattern: keil_connect, keil_run, keil_read_variable). All have descriptions (avg ~80 chars, baseline 194). However, input schemas are present but minimal: most parameters lack type constraints, enums, or validation guidance. No output schemas documented. Error handling absent, tools return status codes with no recovery guidance. Parameters like 'expression' (keil_set_breakpoint) and 'bytes' (keil_write_memory) lack format/range documentation. No idempotency hints for destructive operations (keil_write_memory, keil_reset). Descriptions are functional but generic, do not explain WHEN to use each tool or dependencies between them (e.g., keil_connect must precede keil_run).
Build the loaded project
Clear a previously set breakpoint
Connect to Keil µVision debugger via UVSC interface
Disconnect from Keil µVision debugger
Enter debug mode for the loaded project
Evaluate an expression in the context of the debugged target
Exit debug mode
No output schemas documented. LLMs cannot infer what fields each tool returns, forcing them to guess downstream field names and risk broken tool chains.
Parameter descriptions lack format/range constraints. 'expression' in keil_set_breakpoint does not specify valid formats (function name, address, file:line). 'bytes' in keil_write_memory lacks byte range (0-255) or array length limits.
No error handling guidance. Tools return status codes (implied from UVSC API) with no recovery hints. LLM cannot distinguish retryable errors from fatal ones or know what to do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2025-06-18+ | v2 |
Get current execution status of the debugged target
Read raw memory from the debugged target
Read the value of a single variable from the debugged target
Read the values of multiple variables from the debugged target
Reset the debugged target
Start execution of the debugged target
Set a breakpoint at a specified location
Execute a single high-level language statement on the debugged target
Execute a single instruction on the debugged target
Stop execution of the debugged target
Write raw memory to the debugged target
Destructive operations (keil_write_memory, keil_reset, keil_build with rebuild=true) lack idempotency hints or confirmation patterns. Agents may retry and cause unintended side effects.
Tool descriptions do not explain dependencies or prerequisites. keil_run requires keil_connect and keil_enter_debug to have been called first, but this is not documented.