Skip to main content
Glama

Kilotest

by com.kilotest
OverviewDiscussionsAdmin

listIssues

Read-onlyIdempotent

Lists the issues reported in one report, along with the history of all reports about the same page. Use this after listPages to switch to an earlier or later report or to begin examining this report. Returns the history and the basics about this report’s issues.

Input Schema

NameRequiredDescriptionDefault
reportIDYesIdentifier of the report (example: 260503T0432-x9z)

Output Schema

NameRequiredDescriptionDefault
tool nameYes
this requestYes
tool collectionYes
response contentYes
response metadataYes
URLs of similar requests for web usersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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: -[
-  "timeStamp",
-  "jobID"
-]New value: +[
+  "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)."
    • changedOutput schema / properties / response content / properties / history of reports about the page / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "completion date and time": {
-          "type": "string"
-        },
-        "days since the report was completed": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "how to get details about the report": {
-          "additionalProperties": false,
-          "properties": {
-            "URL": {
-              "type": "string"
-            },
-            "method": {
-              "const": "GET",
-              "type": "string"
-            }
-          },
-          "required": [
-            "method",
-            "URL"
-          ],
-          "type": "object"
-        },
-        "identifier": {
-          "description": "timeStamp-jobID identifier of the report.",
-          "type": "string"
-        },
-        "web users can get details about the report at": {
-          "type": "string"
-        },
-        "whether it is the latest report about the page": {
-          "type": "boolean"
-        },
-        "whether it is the oldest report about the page": {
-          "type": "boolean"
-        },
-        "whether it is the report described in this response": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "identifier",
-        "completion date and time",
-        "days since the report was completed",
-        "whether it is the oldest report about the page",
-        "whether it is the latest report about the page",
-        "whether it is the report described in this response",
-        "how to get details about the report",
-        "web users can get details about the report at"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "completion date and time": {
+          "type": "string"
+        },
+        "days since the report was completed": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "how to get details about the report": {
+          "additionalProperties": false,
+          "properties": {
+            "URL": {
+              "type": "string"
+            },
+            "method": {
+              "const": "GET",
+              "type": "string"
+            }
+          },
+          "required": [
+            "method",
+            "URL"
+          ],
+          "type": "object"
+        },
+        "identifier": {
+          "description": "Identifier of the report (example: 260503T0432-x9z).",
+          "type": "string"
+        },
+        "web users can get details about the report at": {
+          "type": "string"
+        },
+        "whether it is the latest report about the page": {
+          "type": "boolean"
+        },
+        "whether it is the oldest report about the page": {
+          "type": "boolean"
+        },
+        "whether it is the report described in this response": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "identifier",
+        "completion date and time",
+        "days since the report was completed",
+        "whether it is the oldest report about the page",
+        "whether it is the latest report about the page",
+        "whether it is the report described in this response",
+        "how to get details about the report",
+        "web users can get details about the report at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / response content / properties / history of reports about the page
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "completion date and time": {
+            "type": "string"
+          },
+          "days since the report was completed": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "how to get details about the report": {
+            "additionalProperties": false,
+            "properties": {
+              "URL": {
+                "type": "string"
+              },
+              "method": {
+                "const": "GET",
+                "type": "string"
+              }
+            },
+            "required": [
+              "method",
+              "URL"
+            ],
+            "type": "object"
+          },
+          "identifier": {
+            "description": "timeStamp-jobID identifier of the report.",
+            "type": "string"
+          },
+          "web users can get details about the report at": {
+            "type": "string"
+          },
+          "whether it is the latest report about the page": {
+            "type": "boolean"
+          },
+          "whether it is the oldest report about the page": {
+            "type": "boolean"
+          },
+          "whether it is the report described in this response": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "identifier",
+          "completion date and time",
+          "days since the report was completed",
+          "whether it is the oldest report about the page",
+          "whether it is the latest report about the page",
+          "whether it is the report described in this response",
+          "how to get details about the report",
+          "web users can get details about the report at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "All reports about the same page, from oldest to latest, or null if the report is unavailable."
+}
    • changedOutput schema / properties / response content / required
      Previous value: -[
-  "basics about the report",
-  "details about the report",
-  "how to request that the page be retested",
-  "how a web user can request that the page be retested",
-  "how to get the full report in JSON",
-  "how a web user can get the full report in JSON",
-  "basics about all issues reported in the report"
-]New value: +[
+  "basics about the report",
+  "history of reports about the page",
+  "details about the report",
+  "how to request that the page be retested",
+  "how a web user can request that the page be retested",
+  "how to get the full report in JSON",
+  "how a web user can get the full report in JSON",
+  "basics about all issues reported in the report"
+]
  3. Changed2 schema fields changed
    • removedOutput schema / definitions / RequestReference / properties / method / const
      Removed value: -"GET"
    • addedOutput schema / definitions / RequestReference / properties / method / enum
      Added value: +[
+  "GET",
+  "POST"
+]
  4. Changed4 schema fields changed
    • 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 issues reported in the report / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "how to get details about the issue": {
+          "additionalProperties": false,
+          "properties": {
+            "URL": {
+              "type": "string"
+            },
+            "method": {
+              "const": "GET",
+              "type": "string"
+            }
+          },
+          "required": [
+            "method",
+            "URL"
+          ],
+          "type": "object"
+        },
+        "identifier": {
+          "type": "string"
+        },
+        "impact on a user": {
+          "type": "string"
+        },
+        "priority": {
+          "enum": [
+            "lowest",
+            "low",
+            "high",
+            "highest"
+          ],
+          "type": "string"
+        },
+        "rule engines with any violations belonging to the issue": {
+          "items": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "web users can get details about the issue at": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "identifier",
+        "summary",
+        "impact on a user",
+        "priority",
+        "rule engines with any violations belonging to the issue",
+        "how to get details about the issue",
+        "web users can get details about the issue at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / response content / properties / basics about all issues reported in the report / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "how to get details about the issue": {
-      "additionalProperties": false,
-      "properties": {
-        "URL": {
-          "type": "string"
-        },
-        "method": {
-          "const": "GET",
-          "type": "string"
-        }
-      },
-      "required": [
-        "method",
-        "URL"
-      ],
-      "type": "object"
-    },
-    "identifier": {
-      "type": "string"
-    },
-    "impact on a user": {
-      "type": "string"
-    },
-    "priority": {
-      "enum": [
-        "lowest",
-        "low",
-        "high",
-        "highest"
-      ],
-      "type": "string"
-    },
-    "rule engines with any violations belonging to the issue": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "summary": {
-      "type": "string"
-    },
-    "web users can get details about the issue at": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "identifier",
-    "summary",
-    "impact on a user",
-    "priority",
-    "rule engines with any violations belonging to the issue",
-    "how to get details about the issue",
-    "web users can get details about the issue at"
-  ],
-  "type": "object"
-}
    • removedOutput schema / properties / response content / properties / basics about all issues reported in the report / type
      Removed value: -"array"
  5. First observed

TDQS

A3.9/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 openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the response includes the history of all reports about the same page, not just this report's issues, which is real context beyond the annotations.

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 core action and result, and the second sentence earns its place by giving the usage sequence. Slightly dense phrasing ('the history and the basics about this report's issues') but no wasted text.

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 detail is not required in the description. Given the single-parameter, read-only nature and full annotation coverage, the description supplies enough to call it correctly, though the relationship to the other list* siblings remains unstated.

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?

There is a single required parameter with 100% schema coverage and an example format, so the schema carries the semantic load. The description only says 'one report,' adding nothing about format or valid values beyond what the schema provides — the baseline 3 for high coverage.

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 and resource ('Lists the issues reported in one report') and adds the notable scope detail that it also returns report history for the same page. It does not explicitly distinguish itself from siblings like listDiagnoses or listViolators, which also sound issue-adjacent, so it falls short of a 5.

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 listPages to switch to an earlier or later report or to begin examining this report' gives a clear entry condition and workflow position. It lacks explicit when-not guidance or a named alternative, so it is strong but not complete.

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

All Kilotest toolsInspect
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