Skip to main content
Glama

读取命令窗口输出

read_console_output
Read-onlyIdempotent

Retrieve debug output from Keil's command window after executing commands, including breakpoint lists, EVAL results, printf prints, and error lines. Optionally clear the cached output.

Instructions

读取 Keil 命令窗口(Command)的调试输出,来自 UVSOCK 推送的 UV_DBG_CMD_OUTPUT(0x5020) 异步消息。执行 EXEC_CMD / BL / EVAL / 断点 等命令后,其输出(如断点列表、EVAL 结果、printf 调试打印、错误行)通过本工具读取,实现调试信息闭环。clear 可选清空缓存。注意:输出为异步推送,需先执行命令再读;每次发送请求前会自动收集堆积的异步帧。 【参数】必填: 无;可选: clear 【调用示例】{} 【参数别名】clear ← drain/flush/reset。规范名以上方【参数】行为准;未列出的参数名会被拒绝,不会静默忽略

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark the operation read-only and non-destructive, but the description adds meaningful behavior beyond that: output arrives via async push, accumulated frames are automatically collected before each request, and clear empties the cache. This materially helps an agent predict timing and side effects.

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 front-loaded with the core purpose, then covers timing, parameter semantics, and aliases in a structured way. It repeats some schema information in the parameter section, but that redundancy is minor and the section layout helps scannability.

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?

Given this is a one-parameter, low-complexity read tool with an output schema available, the description covers the essential operational context: when to call it, how async output behaves, how caching works, and how to clear it. Nothing critical is missing for the agent to invoke it correctly.

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 input schema only defines clear as a boolean with default false and no description (0% coverage). The description compensates by explaining that clear optionally clears the cache and listing aliases (drain/flush/reset), which is sufficient semantic guidance for this single parameter.

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 states a specific verb and resource: reading Keil Command window debug output. It further identifies the exact async source message (UV_DBG_CMD_OUTPUT 0x5020) and the execution contexts that produce output, distinguishing it from generic siblings like read_async_messages or read_variable.

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 explicitly explains when to use the tool: after EXEC_CMD / BL / EVAL / breakpoint commands, and warns that output is async, so commands must be run first. It does not name alternative tools or state when not to use this tool, but the usage context is clear enough for an agent to route correctly.

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