Argus

Overview Schema Source Related Servers Discussions Admin

Replay Regression Checks

regression_check

Destructive

Re-runs fresh-load checks for findings journaled in earlier runs, classifying each against the current build as still present, no longer reproducing, or inconclusive.

Instructions

Re-run fresh-load checks for findings journaled in earlier runs against the current build: still present, no longer reproduces, or inconclusive. Read-only; replay findings are not re-driven.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "regression_check"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	No
`run_id`	Yes
`stages`	No
`status`	Yes
`recovery`	No
`operation`	Yes
`error_code`	Yes
`session_state`	Yes
`schema_version`	No
`progress_omitted`	No
`progress_delivery_failed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.0Oct 26, 2026
- removedInput schema / title
```
Removed value: -"regression_checkArguments"
```
Changed12 schema fields changedOct 26, 2026
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / properties / error_code / title
```
Removed value: -"Error Code"
```
- removedOutput schema / properties / operation / title
```
Removed value: -"Operation"
```
- removedOutput schema / properties / progress_delivery_failed / title
```
Removed value: -"Progress Delivery Failed"
```
- removedOutput schema / properties / progress_omitted / title
```
Removed value: -"Progress Omitted"
```
- removedOutput schema / properties / recovery / title
```
Removed value: -"Recovery"
```
- removedOutput schema / properties / run_id / title
```
Removed value: -"Run Id"
```
- removedOutput schema / properties / schema_version / title
```
Removed value: -"Schema Version"
```
- removedOutput schema / properties / session_state / title
```
Removed value: -"Session State"
```
- removedOutput schema / properties / stages / title
```
Removed value: -"Stages"
```
- removedOutput schema / properties / status / title
```
Removed value: -"Status"
```
- removedOutput schema / title
```
Removed value: -"AgentResult"
```

Changed14 schema fields changedv0.5.2Oct 26, 2026

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": true,
+  "title": "Data",
+  "type": "object"
+}

addedOutput schema / properties / error_code

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Error Code"
+}

addedOutput schema / properties / operation

Added value: +{
+  "title": "Operation",
+  "type": "string"
+}

addedOutput schema / properties / progress_delivery_failed

Added value: +{
+  "default": false,
+  "title": "Progress Delivery Failed",
+  "type": "boolean"
+}

addedOutput schema / properties / progress_omitted

Added value: +{
+  "default": 0,
+  "title": "Progress Omitted",
+  "type": "integer"
+}

addedOutput schema / properties / recovery

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Recovery",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / run_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Run Id"
+}

addedOutput schema / properties / schema_version

Added value: +{
+  "const": 1,
+  "default": 1,
+  "title": "Schema Version",
+  "type": "integer"
+}

addedOutput schema / properties / session_state

Added value: +{
+  "title": "Session State",
+  "type": "string"
+}

addedOutput schema / properties / stages

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Stages",
+  "type": "array"
+}

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "completed",
+    "error"
+  ],
+  "title": "Status",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "operation",
+  "status",
+  "session_state",
+  "run_id",
+  "error_code"
+]

changedOutput schema / title

Previous value: -"regression_checkOutput"New value: +"AgentResult"

Addedv0.5.1Jul 21, 2026

TDQS

C2.9/5.0

Behavior1/5

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

The description declares 'Read-only', while the annotations set readOnlyHint=false and destructiveHint=true — a direct conflict about the tool's side effects. With openWorldHint=true and non-idempotent replay behavior also unaddressed, an agent cannot tell whether calling this mutates state.

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?

Two sentences, front-loaded with the core operation, which is appropriately sized. However, the second sentence spends half the description on a 'Read-only' claim that is contradicted by the annotations, so it does not earn its place.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But for a tool annotated destructive and open-world, the description never says what gets changed or whether prior journal entries are overwritten by the replay, and its false read-only claim actively misleads.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The stated outcomes ('still present, no longer reproduces, or inconclusive') are the only meaningful semantics, and they are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Re-run fresh-load checks for findings journaled in earlier runs against the current build') and enumerates the three possible verdicts, which separates it from sibling verification tools like verify_persistence or test_action. It stops short of naming an explicit alternative, but the operation is unmistakable.

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

Usage Guidelines3/5

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

'For findings journaled in earlier runs' implies the precondition (prior findings must exist) and thus when to invoke it, but there is no explicit when-not guidance and no routing to or away from siblings such as verify_persistence or observe. Usage is inferable rather than stated.

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