取得某使用者當前頁面的即時 Console/Network 錯誤（需 user_email + session_token 驗證身分）。Live console/network errors — requires user_email and session_token.
| Name | Required | Description | Default |
|---|---|---|---|
| user_email | Yes | 你的 BugEzy email（只讀你自己的即時錯誤） | |
| session_token | No | BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that authentication via user_email and session_token is required and that it targets the current page. However, with no annotations, it does not mention whether the operation is read-only, the response format, or error handling behavior, leaving gaps for a potentially risky operation.
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 short and front-loaded, but it duplicates the same information in Chinese and English, making it slightly redundant. It contains no fluff and earns its place, though the bilingual repetition could be streamlined.
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 a simple tool with two parameters and no output schema, the description covers the core purpose and auth requirement. However, it does not describe the output format or how console and network errors are combined, which could be relevant for an agent invoking the tool.
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 descriptions already cover both parameters with clear details, including the optionality of session_token when a token is present in the MCP URL. The tool description merely restates 'requires user_email and session_token' without adding new semantic value beyond the schema.
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 clearly states 'Live console/network errors' and specifies 'current page' and scope, making the action and resource evident. However, it does not explicitly differentiate from sibling tools like get_console_logs or get_network_errors, which could overlap.
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?
No guidance is provided about when to use this tool versus the separate console or network error tools. The description only states what it does, not the appropriate context or alternatives, leaving the agent to infer usage.
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.