Analyze multiple JUnit XML reports with Markov chain transition matrices to detect unstable tests, quantify flakiness, and identify quarantine candidates.
Analyze test stability from multiple JUnit XML runs using Markov chain transition matrices.
| Name | Required | Description | Default |
|---|---|---|---|
| junitXmlReports | Yes | Array of JUnit XML report strings |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the analytical method (Markov chain transition matrices) but omits whether the operation is read-only, what the output contains, computational cost, or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that is appropriately sized for a one-parameter tool. There is no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description should explain what the analysis returns (e.g., stability metrics, flaky test lists). It also does not clarify the 'quarantine' aspect implied by the tool name, leaving the definition incomplete for an analysis tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single parameter is fully described in the schema. The description adds no new parameter details, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Analyze'), resource ('test stability'), input source ('multiple JUnit XML runs'), and method ('Markov chain transition matrices'). It is clear enough to distinguish from the unrelated sibling tools, though it does not specify what aspect of stability is reported.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, prerequisites, or alternatives are provided. The description offers no context about when this analysis is appropriate or what to do with its results.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.