Umtri

List bugs of a ground

list_bugs

Scans the bugs (issues eroding the ground) of one ground. Looking at ONE bug you already know the number/id of? Call get_bug instead — no need to list. Bugs default to status="active" (wild + chasing): a healed bug is history, and history is not what a scan is for. Ask for "resolved" or "all" when you actually want it. Status speaks the product's own words — wild (found, nobody on it) → chasing (someone is fixing it) → resolved (it landed) — the same words the UI shows. Each bug has a score (0–8 change-risk; 8 = riskiest), and any bug whose solution carries a checklist also carries solutionProgress ("2/5" — ticked/total), so you can see what is left without opening a single body. Targets: a node, an api, or the ground itself. By default returns a summary view — each bug carries id, seq (the number a human says, "#14"), target, title, score, status, createdAt/resolvedAt, plus a 200-char description excerpt. Each node/api bug also carries impactCount — how many other nodes its target reaches by blast radius (affected direction), so you can spot wide-blast bugs at a glance; call get_impact on that bug for the full reached list. Pass view="full" for full descriptions and metadata. Use limit + order to bound a scan (e.g. the 5 newest) instead of pulling every bug.

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": {
      "slug": "<slug>"
    },
    "name": "list_bugs"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Ground slug.
`view`	No	summary (default) for a compact list; full for verbatim descriptions + metadata.
`limit`	No	Return at most this many bugs (applied after the status filter). Omit for all matching.
`order`	No	By creation time: "asc" oldest first (default), "desc" newest first. Pair with limit for "the N newest".
`status`	No	Which bugs to include. Default "active" = wild + chasing (open + in_progress). "wild" = found but untouched, "chasing" = someone is on it, "resolved" = healed (resolved + closed), "all" = every bug. The raw DB statuses are accepted too; note "open" means wild + chasing there (REST semantics), so pass "wild" when you want only the untouched ones.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden and does most of it: it discloses the default filter (active = wild + chasing), the status lifecycle vocabulary, that score is a 0–8 change risk, that solutionProgress appears as "2/5", and the exact difference between the summary and full return shapes. It stops short of permissions/rate-limit behavior, keeping it below a 5 for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the get_bug alternative are correctly front-loaded, but the body is one dense paragraph mixing filtering, status vocabulary, return shape, and blast-radius advice, with some editorializing ("history is not what a scan is for", "without opening a single body") that could be trimmed. It is readable but not structurally organized for fast scanning.

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?

With no output schema and no annotations, the description supplies what is otherwise missing: the default and alternate status values, the fields returned in summary mode (id, seq, target, title, score, status, timestamps, 200-char excerpt), the extra impactCount on node/api bugs, and how view="full" differs. An agent has enough to call it and interpret results correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains why status defaults to active, clarifies the product-vocabulary mapping and the pitfall that "open" means wild+chasing in REST semantics, and shows how limit and order combine for "the 5 newest". The schema still does the heavy lifting on types and enums.

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?

"Scans the bugs (issues eroding the ground) of one ground" gives a specific verb and resource, defines the domain term "bug" inline, and scopes it to a single ground. It immediately distinguishes itself from get_bug ("Looking at ONE bug you already know the number/id of? Call get_bug instead"), so an agent can route without opening either schema.

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?

Explicit when-to-use rules: use get_bug for a known bug rather than listing, and only request "resolved"/"all" when history is actually wanted since the default is status="active". It also names the downstream alternative ("call get_impact on that bug for the full reached list") and prescribes limit+order for bounded scans.

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

All Umtri tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.