keil-mdk-mcp

Overview Schema Source Related Servers Discussions Admin

keil_get_build_log

Reads the latest Keil MDK build log or a named log from server artifacts, returning up to 5,000 lines and a configurable tail for debugging build failures.

Instructions

Read global latest log or a basename from server artifacts/build-logs (1..5000 lines). project_path is optional compatibility metadata, not a filter.

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

Input Schema

Name	Required	Description	Default
`log_name`	No
`tail_lines`	No
`project_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description usefully establishes read-oriented behavior, server-side log scope, latest-log fallback, and a 1..5000-line bound. The compatibility-only role of project_path is an important behavioral caveat, though missing-log or other error behavior is not disclosed.

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 dense sentences front-load the operation and log-selection behavior, then highlight the project_path pitfall. There is no unnecessary wording.

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 three-parameter read tool with an output schema, this supplies nearly everything needed for correct invocation, especially the global scope and project_path caveat. Explicit parameter mapping and brief error or sibling-routing guidance would make it more complete.

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?

Despite 0% schema description coverage, the text indirectly documents log_name through latest-versus-basename selection, tail_lines through the line range, and project_path explicitly as non-filtering metadata. Mapping the first two parameters would be clearer if they were named directly, and basename expectations remain unspecified.

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 clearly states that the tool reads the latest global build log or a specific log from the server's artifacts/build-logs directory. The storage location helps distinguish it from session or status tools, though no sibling is explicitly contrasted.

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?

It gives clear selection context: retrieve the global latest log or identify a specific log by basename, and do not treat project_path as a filter. It does not explicitly say when to prefer siblings such as keil_get_session_log or keil_parse_build_errors.

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