Kilotest

listDiagnoses

Read-onlyIdempotent

Lists the diagnoses that rule engines gave for how one element exhibited one issue in one report. Use this after listViolators to get details about the element as a violator of the issue. Returns, for each rule engine that reported a violation by the element of a rule belonging to the issue, the diagnosis given by the rule engine.

Input Schema

Name	Required	Description
`issueID`	Yes	Issue identifier (example: contrastPoor)
`reportID`	Yes	Identifier of the report (example: 260503T0432-x9z)
`catalogIndex`	Yes	Identifier of the issue-exhibiting element in the catalog of elements on the page (example: 372)

Output Schema

Name	Required	Description	Default
`tool name`	Yes
`this request`	Yes
`tool collection`	Yes
`response content`	Yes
`response metadata`	Yes
`URLs of similar requests for web users`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 1, 2026

addedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / approval
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / confirmation
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / order confirmation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / request confirmation
```
Added value: +{
+  "type": "string"
+}
```

changed

Output schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / required

Previous value: -[
-  "new testing",
-  "retesting",
-  "latency",
-  "confirmation"
-]New value: +[
+  "new testing",
+  "retesting",
+  "approval",
+  "latency",
+  "request confirmation",
+  "order confirmation"
+]

changedOutput schema / properties / response content / properties / diagnoses of how the element exhibited the issue / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "count of violations of the rule by the element": {
-              "type": "number"
-            },
-            "description of the violation": {
-              "description": "Copied from the report instance (what); type not guaranteed."
-            },
-            "identifier of the violated rule": {
-              "description": "Copied from the report instance (ruleID); type not guaranteed."
-            },
-            "severity of the violation on a 0-to-3 scale": {
-              "description": "Copied from the report instance (ordinalSeverity); type not guaranteed."
-            }
-          },
-          "required": [
-            "identifier of the violated rule",
-            "description of the violation",
-            "severity of the violation on a 0-to-3 scale",
-            "count of violations of the rule by the element"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      {
-        "additionalProperties": false,
-        "properties": {
-          "error": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "error"
-        ],
-        "type": "object"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "count of violations of the rule by the element": {
+              "type": "number"
+            },
+            "description of the violation": {
+              "description": "Copied from the report instance (what); type not guaranteed."
+            },
+            "how to report that you disagree with this diagnosis": {
+              "additionalProperties": false,
+              "properties": {
+                "URL": {
+                  "type": "string"
+                },
+                "method": {
+                  "const": "POST",
+                  "type": "string"
+                },
+                "request body": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "engineID": {
+                      "type": "string"
+                    },
+                    "reason": {
+                      "type": "string"
+                    },
+                    "ruleID": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "engineID",
+                    "ruleID",
+                    "reason"
+                  ],
+                  "type": "object"
+                }
+              },
+              "required": [
+                "method",
+                "URL",
+                "request body"
+              ],
+              "type": "object"
+            },
+            "identifier of the rule engine": {
+              "description": "Copied from the report act (which); type not guaranteed."
+            },
+            "identifier of the violated rule": {
+              "description": "Copied from the report instance (ruleID); type not guaranteed."
+            },
+            "severity of the violation on a 0-to-3 scale": {
+              "description": "Copied from the report instance (ordinalSeverity); type not guaranteed."
+            }
+          },
+          "required": [
+            "identifier of the rule engine",
+            "identifier of the violated rule",
+            "description of the violation",
+            "severity of the violation on a 0-to-3 scale",
+            "count of violations of the rule by the element",
+            "how to report that you disagree with this diagnosis"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "error": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "error"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

Changed5 schema fields changedOct 18, 2026

removedInput schema / properties / jobID

Removed value: -{
-  "description": "Job identifier of the report (example: x9z)",
-  "type": "string"
-}

addedInput schema / properties / reportID

Added value: +{
+  "description": "Identifier of the report (example: 260503T0432-x9z)",
+  "type": "string"
+}

removedInput schema / properties / timeStamp

Removed value: -{
-  "description": "Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "catalogIndex",
-  "issueID",
-  "timeStamp",
-  "jobID"
-]New value: +[
+  "catalogIndex",
+  "issueID",
+  "reportID"
+]

changedOutput schema / definitions / ReportBasics / properties / identifier / description

Previous value: -"timeStamp-jobID identifier of the report."New value: +"Identifier of the report (example: 260503T0432-x9z)."

Changed2 schema fields changedOct 2, 2026
- removedOutput schema / definitions / RequestReference / properties / method / const
```
Removed value: -"GET"
```
- addedOutput schema / definitions / RequestReference / properties / method / enum
```
Added value: +[
+  "GET",
+  "POST"
+]
```

Changed2 schema fields changedSep 15, 2026

changedOutput schema / definitions / ReportBasics / properties / days since the report was completed / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / response content / properties / diagnoses of how the element exhibited the issue / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "count of violations of the rule by the element": {
-          "type": "number"
-        },
-        "description of the violation": {
-          "description": "Copied from the report instance (what); type not guaranteed."
-        },
-        "identifier of the violated rule": {
-          "description": "Copied from the report instance (ruleID); type not guaranteed."
-        },
-        "severity of the violation on a 0-to-3 scale": {
-          "description": "Copied from the report instance (ordinalSeverity); type not guaranteed."
-        }
-      },
-      "required": [
-        "identifier of the violated rule",
-        "description of the violation",
-        "severity of the violation on a 0-to-3 scale",
-        "count of violations of the rule by the element"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "count of violations of the rule by the element": {
+              "type": "number"
+            },
+            "description of the violation": {
+              "description": "Copied from the report instance (what); type not guaranteed."
+            },
+            "identifier of the violated rule": {
+              "description": "Copied from the report instance (ruleID); type not guaranteed."
+            },
+            "severity of the violation on a 0-to-3 scale": {
+              "description": "Copied from the report instance (ordinalSeverity); type not guaranteed."
+            }
+          },
+          "required": [
+            "identifier of the violated rule",
+            "description of the violation",
+            "severity of the violation on a 0-to-3 scale",
+            "count of violations of the rule by the element"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "error": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "error"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile needs no restating. The description adds real value by disclosing the result's cardinality rule: one diagnosis per rule engine that reported a violation of a rule belonging to the issue. It does not discuss failure modes or pagination, but those are minor against full annotation coverage.

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 purpose sentence is front-loaded and the workflow hint follows immediately and usefully. The third sentence largely re-expresses the first in per-rule-engine terms, so there is mild redundancy, but nothing is padding.

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?

An output schema exists, so return-value shape need not be explained, and the description still conveys the per-rule-engine iteration structure and its place in the listViolators workflow. What a 'diagnosis' actually contains is left to the output schema, which is acceptable.

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 all three parameters carry examples, so the schema does the heavy lifting. The narrative maps conceptually onto element, issue and report but adds no format or constraint detail beyond what the schema already provides. Baseline 3 applies.

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 states a specific verb and resource ('Lists the diagnoses that rule engines gave') and pins the scope to one element, one issue, one report. This clearly separates it from listIssues and listViolators, which operate at issue and violator granularity respectively.

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?

It explicitly names the prerequisite workflow: 'Use this after listViolators to get details about the element as a violator of the issue.' That is a clear sequencing signal rather than an inferred one. It stops short of stating when not to use the tool or naming a direct alternative for diagnosis data.

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

All Kilotest tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.