Release Readiness Triage MCP

aggregate_suite_failures

Group CI test failures by error signature, deduplicate repeats, and classify as assertion, timeout, network, or crash to streamline release readiness triage.

Instructions

Parse a CI test run and group failures by error signature. Deduplicates repeated errors and categorizes them as assertion, timeout, network, or crash. Use this as the first step before triage.

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": {
      "failures": "<failures>",
      "totalTests": "<totalTests>",
      "passedTests": "<passedTests>"
    },
    "name": "aggregate_suite_failures"
  }
}

Input Schema

Name	Required	Description
`runId`	No	CI run identifier
`branch`	No	Branch name
`failures`	Yes	List of test failures from the CI run
`commitSha`	No	Commit SHA
`totalTests`	Yes	Total number of tests in the run
`passedTests`	Yes	Number of tests that passed
`customInfraPatterns`	No	Extra regex patterns (as strings) to classify as infrastructure errors, e.g. cloud-provider-specific messages like 'No space left on device' or 'GCP quota exceeded'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently states key behaviors: parsing, grouping by error signature, deduplicating repeated errors, and categorizing into four specific types. It does not mention return format or side effects, but the core behavior is well covered.

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 three sentences with zero fluff. It front-loads the primary purpose, then adds behavioral detail, then a usage directive. Every sentence earns its place and the length is appropriate for the tool's complexity.

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?

The tool has 7 parameters, no annotations, and no output schema, so the description needs to convey both input handling and expected results. While it explains the grouping/categorization logic, it omits details like the output structure and does not mention the extensibility via customInfraPatterns. The description is adequate but leaves gaps that an agent would need to infer.

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 baseline is 3. The description adds no parameter-level detail beyond what the schema already provides, and it does not reference parameters like customInfraPatterns or runId. It neither enhances nor harms the semantic understanding.

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 uses a specific verb and resource ('Parse a CI test run and group failures by error signature') and clearly distinguishes the tool from siblings by detailing its deduplication and categorization behaviors (assertion, timeout, network, crash). This uniquely positions it as an aggregation/pre-processing tool.

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

Usage Guidelines4/5

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

The description provides a clear usage context with 'Use this as the first step before triage,' implying it precedes other analysis tools. However, it lacks explicit alternatives or when-not-to-use conditions, so it stops short of the top anchor.

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

Deploy Server