Skip to main content
Glama
keil-mdk-mcp

keil-mdk-mcp

by lideshengstu

keil_rebuild

Performs a full Keil MDK rebuild with UV4 -r, requiring fresh expected output alongside build logs and exit evidence to verify the project builds correctly.

Instructions

UV4 -r full rebuild; require fresh expected output in addition to log/exit evidence.

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

Input Schema

NameRequiredDescriptionDefault
targetNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.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 UV4 "-r" mechanism and requires fresh expected output in addition to log and exit evidence. It does not explain filesystem or artifact side effects, project/target resolution, or other invocation prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the command and full-rebuild behavior, with no filler. Its telegraphic phrasing and the ambiguous term "expected output" reduce immediate clarity.

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

Completeness2/5

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

The output schema reduces the need to describe return values, but the definition remains incomplete for a parameterized build operation. Missing parameter semantics, default behavior, prerequisites, and sibling-selection guidance leave substantial invocation ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain either target or project_path. It also leaves their null defaults, accepted values, and discovery or fallback behavior undocumented.

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 description identifies a specific operation, a "UV4 -r full rebuild," and "full" implicitly distinguishes it from the sibling keil_build tool. It does not explicitly name the project or build artifacts being rebuilt, but the purpose is clear in the Keil context.

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?

The tool is implicitly appropriate when a full rebuild and fresh-output verification are needed. However, it gives no explicit guidance on when to choose it over keil_build, nor any prerequisites for invoking it.

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