Skip to main content
Glama
amenalahassa

bugcap

by amenalahassa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List bug reports

list_reports
Read-only

List bug reports stored locally by bugcap, newest first, to find a report ID. Filter by status, repo scope, or limit; returns summaries only, so fetch full details separately.

Instructions

List bug reports stored by bugcap, newest first. Use this to find a report id; it returns only summaries (id, title, status, tags, repo, created_at, linked GitHub issue) and no notes or images, so call get_report for the full report. Read-only and local: no network access. Returns a JSON array, empty when nothing matches.

Input Schema

NameRequiredDescriptionDefault
allNofalse (default): only reports filed for the repo the server runs in. true: every repo.
limitNoReturn at most this many reports, newest first.
statusNoKeep only reports with this status. Default: every status.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.2
    • addedInput schema / properties / all / description
      Added value: +"false (default): only reports filed for the repo the server runs in. true: every repo."
    • addedInput schema / properties / limit / description
      Added value: +"Return at most this many reports, newest first."
    • changedInput schema / properties / status / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "open",
+      "in-progress",
+      "resolved",
+      "closed",
+      "wontfix"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / status / description
      Added value: +"Keep only reports with this status. Default: every status."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description largely restates that ('read-only and local: no network access') rather than adding new safety facts. It does add genuinely new behavior, though: it enumerates the exact summary fields returned, warns that notes and images are omitted, and states that an empty JSON array is returned when nothing matches.

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?

Four short sentences, front-loaded with the purpose, then the return shape, the alternative, and the safety note. Nothing is buried and no sentence is filler, aside from a mild restatement of read-only.

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?

An output schema exists, yet the description still summarizes the returned summary fields and the empty-result case, and it points to get_report for full detail. Combined with full parameter coverage in the schema, an agent has everything needed to call it correctly.

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 all three parameters (all, limit, status) are already fully documented in the schema. The description only echoes the ordering implied by 'limit' ('newest first') and says nothing about the repo-scope flag 'all' or status filtering, so it adds little beyond the schema.

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?

States a specific verb and resource ('List bug reports stored by bugcap') plus ordering ('newest first'). It also carves out exactly what the sibling get_report does instead, so the agent can distinguish the two without inspecting schemas.

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

Usage Guidelines5/5

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

Explicitly says the intended use is 'to find a report id' and names the alternative ('call get_report for the full report') with the condition that selects it (need notes/images). This is a clear when-to-use plus when-to-use-something-else routing statement.

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