Mushi-Mushi

Gate findings

list_gate_findings

Read-onlyIdempotent

List recent CI gate runs and findings for a project, newest first. Filter by gate or severity to see which checks failed on the last crawl.

Instructions

List recent inventory gate runs and their findings for a project, newest first. Returns { runs: [{ id, gate, status, findings_count, … }], findings: [{ severity, rule_id, message, file_path, node_id, … }] }. Filter by gate (dead_handler | mock_leak | api_contract | crawl | status_claim | spec_drift | orphan_endpoint | unknown_call | schema_drift | code_health) or finding severity (info | warn | error). Read-only. Use to see which CI gates failed on the last crawl; use diff_inventory to compare two commits, or get_inventory for the full snapshot.

Input Schema

TableJSON Schema

Name	Required	Description
`gate`	No	Only runs of this gate (and their findings).
`severity`	No	Only findings with exactly this severity.
`projectId`	No	Project UUID — defaults to configured project (`project_id` is accepted too.)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`runs`	Yes	Recent gate_runs rows, newest first
`findings`	Yes	gate_findings rows for those runs

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.12Sep 24, 2026

changedInput schema / properties / gate / description

Previous value: -"Filter to one gate id: dead-handler | mock-leak | crawl | status-claim"New value: +"Only runs of this gate (and their findings)."

addedInput schema / properties / gate / enum

Added value: +[
+  "dead_handler",
+  "mock_leak",
+  "api_contract",
+  "crawl",
+  "status_claim",
+  "spec_drift",
+  "orphan_endpoint",
+  "unknown_call",
+  "schema_drift",
+  "code_health"
+]

changedInput schema / properties / projectId / description

Previous value: -"Project UUID — defaults to configured project"New value: +"Project UUID — defaults to configured project (`project_id` is accepted too.)"

changedInput schema / properties / severity / description

Previous value: -"Minimum severity to include: low | medium | high | critical"New value: +"Only findings with exactly this severity."

addedInput schema / properties / severity / enum

Added value: +[
+  "info",
+  "warn",
+  "error"
+]

Changed2 schema fields changedv0.1.10Sep 15, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Addedv0.1.2Jun 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and openWorldHint, so the description doesn't need to re-derive safety. It adds value by disclosing the newest-first ordering, the returned runs/findings shape, and the available gate/severity filters. The explicit 'Read-only' line is redundant with annotations but not contradictory.

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 front-loaded with the core purpose, followed by the return shape, filters, and sibling routing. It is slightly dense because it repeats the full enum lists that the schema already provides, but every sentence carries functional value and it remains compact.

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

Completeness4/5

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

For a read-only list tool with three optional, fully documented parameters and an output schema, the description covers purpose, ordering, return shape, filters, and alternatives. 'Recent' is not precisely bounded and pagination is not mentioned, but those are minor gaps given the output schema and annotation coverage.

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%, and both gate and severity already carry enums and meaningful descriptions. The description restates the filter options and maps them to the conceptual purpose, but it doesn't add substantial meaning beyond the schema, so the high-coverage 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 opens with a specific verb and resource: 'List recent inventory gate runs and their findings for a project, newest first.' It clearly differentiates the tool from siblings by explicitly naming diff_inventory and get_inventory as alternatives for different tasks.

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?

It provides direct usage guidance: 'Use to see which CI gates failed on the last crawl; use diff_inventory to compare two commits, or get_inventory for the full snapshot.' This tells the agent exactly when to pick this tool over nearby alternatives, with no ambiguity.

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