取得一份報告的完整時間軸（時序麵包屑）。把 Console、Network、語音、標記、網路環境、儲存狀態全部按時間排序成一條故事線，AI 只需呼叫這一個 tool 就能掌握完整 Bug 脈絡（省去逐一呼叫 console/network/voice 各 tool）。Full report timeline.
| Name | Required | Description | Default |
|---|---|---|---|
| report_id | Yes | 報告 ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that the tool combines and chronologically sorts multiple data types, which is a valuable behavioral trait. However, it does not mention whether it's read-only, how it handles missing reports, or the exact output structure, leaving some transparency gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose but includes a redundant final sentence 'Full report timeline' that repeats the preceding Chinese text, adding no new information. It could be trimmed without loss of meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For an aggregate tool with no output schema, the description explains what data sources are included and that the result is a complete chronological storyline. It could be more specific about the return format, but the description gives enough context for an AI to understand the tool's role and scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter (report_id), and the schema already provides a clear description. The tool description does not add further parameter meaning, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: '取得一份報告的完整時間軸' (get a report's complete timeline). It also clearly differentiates from sibling tools by listing the included data types (Console, Network, voice, markers, network environment, storage) and explicitly noting it avoids calling individual tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly recommends using this tool to grasp the complete bug context and explicitly names the alternative approach of calling console/network/voice tools individually. However, it lacks an explicit 'when not to use' statement, so it's not a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools are mostly distinct, but there is some overlap between get_console_logs, get_network_errors, and get_live_errors, as get_live_errors encompasses the other two. Also, get_rrweb_events and get_rrweb_summary serve similar purposes, though one is full data and the other a summary.
All tools follow the verb_noun pattern with lowercase underscores, using 'get_' for retrieving specific data and 'list_' for listing reports. This is a consistent and predictable naming convention.
Thirteen tools is well within the typical range for a comprehensive debugging server. Each tool serves a specific purpose, and there are no redundant or unnecessary tools.
The tool set provides thorough coverage of the debugging workflow, including console, network, terminal, DOM events, screenshots, voice transcripts, and a unified timeline. It also includes report listing and usage stats, leaving no obvious gaps for its stated purpose.