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.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so safety is covered. The description adds that this is a drill-down producing per-rule-engine diagnoses, but says nothing about pagination, ordering, auth, or what happens when the element has no violation (empty result).

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?

Two sentences, front-loaded with the what-and-scope before the usage note. The second sentence restates the first's content fairly closely (per-rule-engine diagnosis output), which is mild redundancy.

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 values need not be explained, and annotations carry the safety profile. The description covers what it returns, at what granularity, and how it fits after listViolators, leaving only edge-case behavior (empty results, error conditions) unspecified.

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 issueID, reportID, and catalogIndex are already documented in the schema with examples. The description clarifies the role of catalogIndex ("the issue-exhibiting element") but adds no format or syntax beyond the schema. Baseline 3 applies.

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?

States a specific verb ("Lists") and resource ("diagnoses") with a precise scope: one element, one issue, one report. An agent can distinguish it from listViolators, though the second sentence largely re-describes the same return content rather than sharpening the purpose.

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?

"Use this after listViolators to get details about the element as a violator of the issue" gives explicit sequencing and names the alternative sibling. It lacks a when-not condition, but the workflow position is unambiguous.

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

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?