Kilotest

listViolators

Read-onlyIdempotent

Lists the elements of a tested page that were reported as exhibiting one issue in one report. Use this after listIssues to drill down from an issue to the elements violating rules belonging to that issue. Returns basics about each violating element.

Input Schema

Name	Required	Description	Default
`issueID`	Yes	Issue identifier (example: contrastPoor)
`reportID`	Yes	Identifier of the report (example: 260503T0432-x9z)

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 / basics about all elements exhibiting the issue / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "count of rule engines reporting that the element exhibited the issue": {
-          "type": "number"
-        },
-        "how to get details about the element": {
-          "additionalProperties": false,
-          "properties": {
-            "URL": {
-              "type": "string"
-            },
-            "request method": {
-              "const": "GET",
-              "type": "string"
-            }
-          },
-          "required": [
-            "URL",
-            "request method"
-          ],
-          "type": "object"
-        },
-        "identifier": {
-          "description": "Catalog index of the element in the report; a string or number, copied verbatim.",
-          "type": [
-            "string",
-            "number"
-          ]
-        },
-        "inner text": {
-          "description": "Copied from the report catalog entry; type not guaranteed."
-        },
-        "tag name": {
-          "description": "Copied from the report catalog entry; type not guaranteed."
-        },
-        "web users can get details about the element at": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "identifier",
-        "tag name",
-        "inner text",
-        "count of rule engines reporting that the element exhibited the issue",
-        "how to get details about the element",
-        "web users can get details about the element at"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "count of rule engines reporting that the element exhibited the issue": {
+          "type": "number"
+        },
+        "how to get details about the element": {
+          "additionalProperties": false,
+          "properties": {
+            "URL": {
+              "type": "string"
+            },
+            "method": {
+              "const": "GET",
+              "type": "string"
+            }
+          },
+          "required": [
+            "method",
+            "URL"
+          ],
+          "type": "object"
+        },
+        "identifier": {
+          "description": "Catalog index of the element in the report; a string or number, copied verbatim.",
+          "type": [
+            "string",
+            "number"
+          ]
+        },
+        "inner text": {
+          "description": "Copied from the report catalog entry; type not guaranteed."
+        },
+        "tag name": {
+          "description": "Copied from the report catalog entry; type not guaranteed."
+        },
+        "web users can get details about the element at": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "identifier",
+        "tag name",
+        "inner text",
+        "count of rule engines reporting that the element exhibited the issue",
+        "how to get details about the element",
+        "web users can get details about the element at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "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: -[
-  "issueID",
-  "timeStamp",
-  "jobID"
-]New value: +[
+  "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"
+]
```

Changed4 schema fields changedSep 15, 2026

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

addedOutput schema / properties / response content / properties / basics about all elements exhibiting the issue

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count of rule engines reporting that the element exhibited the issue": {
+            "type": "number"
+          },
+          "how to get details about the element": {
+            "additionalProperties": false,
+            "properties": {
+              "URL": {
+                "type": "string"
+              },
+              "request method": {
+                "const": "GET",
+                "type": "string"
+              }
+            },
+            "required": [
+              "URL",
+              "request method"
+            ],
+            "type": "object"
+          },
+          "identifier": {
+            "description": "Catalog index of the element in the report; a string or number, copied verbatim.",
+            "type": [
+              "string",
+              "number"
+            ]
+          },
+          "inner text": {
+            "description": "Copied from the report catalog entry; type not guaranteed."
+          },
+          "tag name": {
+            "description": "Copied from the report catalog entry; type not guaranteed."
+          },
+          "web users can get details about the element at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "identifier",
+          "tag name",
+          "inner text",
+          "count of rule engines reporting that the element exhibited the issue",
+          "how to get details about the element",
+          "web users can get details about the element at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

removedOutput schema / properties / response content / properties / basics about all elements reported as exhibiting the issue

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "count of rule engines reporting that the element exhibited the issue": {
-            "type": "number"
-          },
-          "how to get details about the element": {
-            "additionalProperties": false,
-            "properties": {
-              "URL": {
-                "type": "string"
-              },
-              "request method": {
-                "const": "GET",
-                "type": "string"
-              }
-            },
-            "required": [
-              "URL",
-              "request method"
-            ],
-            "type": "object"
-          },
-          "identifier": {
-            "type": "string"
-          },
-          "inner text": {
-            "description": "Copied from the report catalog entry; type not guaranteed."
-          },
-          "tag name": {
-            "description": "Copied from the report catalog entry; type not guaranteed."
-          },
-          "web users can get details about the element at": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "identifier",
-          "tag name",
-          "inner text",
-          "count of rule engines reporting that the element exhibited the issue",
-          "how to get details about the element",
-          "web users can get details about the element at"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

changedOutput schema / properties / response content / required

Previous value: -[
-  "basics about the report",
-  "basics about the issue",
-  "details about the issue",
-  "basics about all elements reported as exhibiting the issue"
-]New value: +[
+  "basics about the report",
+  "basics about the issue",
+  "details about the issue",
+  "basics about all elements exhibiting the issue"
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description's only addition is that it 'Returns basics about each violating element,' which is thin and partly redundant with the output schema. Useful as a hint about result shape, but no pagination, ordering, or volume expectations are disclosed.

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?

Three short sentences, zero waste, with the scoping definition front-loaded and the routing guidance immediately after. Nothing repeats the annotations or restates the tool name unproductively.

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

Completeness5/5

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

For a two-parameter, read-only list tool whose safety profile is annotation-covered and whose return shape is defined by an output schema, the description supplies everything needed: what is listed, how it is scoped, and when to reach for it. No material gap remains.

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 coverage is 100% and both parameters carry examples ('contrastPoor', '260503T0432-x9z'), so the schema does the heavy lifting. The description adds the relationship between the two parameters – one issue within one report – but no format or provenance detail beyond that. 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?

States a specific verb ('Lists') and resource ('elements of a tested page') plus the exact scoping condition: elements exhibiting one issue in one report. It also distinguishes itself from the sibling listIssues by framing itself as the drill-down step from an issue, so an agent can separate the two without opening either schema.

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?

Explicit sequencing guidance: 'Use this after listIssues to drill down from an issue to the elements violating rules belonging to that issue.' That names the alternative and the condition that selects this tool. It stops short of any when-not-to-use case (e.g. what to do if you lack an issueID), so it is a 4 rather than a 5.

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.