Skip to main content
Glama
Sign In
bugezy

bugezy

by fox100039-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_network_errors

Retrieve 4xx and 5xx network errors from a bug report to identify server-side issues causing the bug.

Instructions

取得報告中的 Network 錯誤（4xx/5xx）。Get network errors (4xx/5xx).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "report_id": "<report_id>"
    },
    "name": "get_network_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYes報告 ID（report_id）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the tool fetches errors, with no mention of side effects, auth requirements, rate limits, or return characteristics. The minimal description adds little transparency.

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 very short, but every word is functional. It is not structured beyond a single line, but conciseness is preserved. Could be improved with a brief front-loaded summary, but current form is not wasteful.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema, the description is adequate but minimal. It specifies the error range (4xx/5xx) but does not explain the output format or any pagination. It is sufficient for basic understanding but lacks completeness.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the single required parameter report_id. The description does not add any additional meaning or examples beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool retrieves network errors (4xx/5xx) from a report. The verb 'get' and the specific resource 'network errors with status codes 4xx/5xx' differentiate it from sibling tools like get_console_logs or get_page_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent is left to infer usage from the name alone.

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

Deploy Server

Other Tools