Skip to main content
Glama
Sign In
bugezy

bugezy

by fox100039-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_report_overview

Retrieve metadata and field counts of a bug report to quickly understand its structure and data volume.

Instructions

取得報告概覽（metadata + 各欄位筆數，不含原始資料）。Get report overview (metadata + counts).

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

Input Schema

NameRequiredDescriptionDefault
report_idYes報告 ID（report_id）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Without annotations, the description carries the burden and clearly specifies the output: metadata and counts, no raw data. It implies a safe read operation, but does not explicitly state whether it is idempotent or the data source. However, for a simple retrieval tool, this is reasonably transparent.

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?

The description is two short sentences (Chinese and English) that convey the same information efficiently with no redundancy or fluff. It is front-loaded and every word serves a purpose.

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?

Given the lack of output schema, the description provides a high-level overview but lacks detail on the structure of metadata and counts. For an agent to fully understand the return value, more specificity is needed. Sibling tools suggest a context of report analysis, but the description is incomplete without output schema.

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?

The input schema has 100% coverage with a brief description for report_id. The tool description adds no additional meaning beyond the schema, such as format or example values. Since schema already defines the parameter, a baseline of 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 returns a report overview with metadata and counts per field, explicitly excluding raw data. This specific verb-resource combination distinguishes it from sibling tools like list_reports (listing reports) and get_console_logs (specific logs).

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

Usage Guidelines3/5

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

The description implies that for raw data other tools should be used by stating '不含原始資料' (without raw data), but it does not explicitly mention when to use this tool or name alternatives. No direct guidance on prerequisites or comparison with siblings is provided.

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