Skip to main content
Glama
Sign In

Kilotest

by io.github.jrpool
OverviewDiscussionsAdmin

listPages

Read-onlyIdempotent

Lists all pages Kilotest has tested. Use this first to discover whether a page already has any reports before requesting a test. Returns, for each tested page, its description, URL, and the identifier of its latest available report.

Input Schema

NameRequiredDescriptionDefault

No arguments

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. Changed17 schema fields changed
    • 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"
+}
    • changedOutput 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"
+]
    • addedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / URL
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / basics about the latest report
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "completion date and time": {
-      "type": "string"
-    },
-    "days since the report was completed": {
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "identifier": {
-      "description": "Identifier of the report (example: 260503T0432-x9z).",
-      "type": "string"
-    }
-  },
-  "required": [
-    "identifier",
-    "completion date and time",
-    "days since the report was completed"
-  ],
-  "type": "object"
-}
    • addedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / description
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / how to get details about the latest report
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "URL": {
-      "type": "string"
-    },
-    "method": {
-      "const": "GET",
-      "type": "string"
-    }
-  },
-  "required": [
-    "method",
-    "URL"
-  ],
-  "type": "object"
-}
    • addedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / identifier
      Added value: +{
+  "description": "Identifier of the latest report about the page (example: 260503T0432-x9z).",
+  "type": "string"
+}
    • removedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / number of reports about the page
      Removed value: -{
-  "type": "number"
-}
    • removedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / tested web page
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "URL": {
-      "type": "string"
-    },
-    "description": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "description",
-    "URL"
-  ],
-  "type": "object"
-}
    • removedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / web users can get details about the latest report at
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / response content / properties / basics about all tested pages / items / required
      Previous value: -[
-  "tested web page",
-  "number of reports about the page",
-  "basics about the latest report",
-  "how to get details about the latest report",
-  "web users can get details about the latest report at"
-]New value: +[
+  "description",
+  "URL",
+  "identifier"
+]
    • addedOutput schema / properties / response content / properties / how to get test results about a page
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "URL": {
+      "description": "URL template; replace {identifier} with the identifier of the latest report about the page.",
+      "type": "string"
+    },
+    "method": {
+      "const": "GET",
+      "type": "string"
+    }
+  },
+  "required": [
+    "method",
+    "URL"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / response content / properties / web users can get test results about a page at
      Added value: +{
+  "description": "URL template; replace {identifier} with the identifier of the latest report about the page.",
+  "type": "string"
+}
    • changedOutput schema / properties / response content / required
      Previous value: -[
-  "basics about all tested pages",
-  "how to request that a page with no report be tested",
-  "how a web user can request that the page be tested"
-]New value: +[
+  "how to get test results about a page",
+  "web users can get test results about a page at",
+  "basics about all tested pages",
+  "how to request that a page with no report be tested",
+  "how a web user can request that the page be tested"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / response content / properties / basics about all tested pages / items / properties / basics about the latest report / properties / identifier / description
      Previous value: -"timeStamp-jobID identifier of the report."New value: +"Identifier of the report (example: 260503T0432-x9z)."
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered; the description adds the useful behavioral detail that each entry carries its latest report identifier, which is the key signal for the discovery workflow. It stops short of noting whether the list is paginated or ordered, which keeps it from a 5.

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: what it does, when to use it, and what comes back. Front-loaded with the action and every sentence earns its place.

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?

An output schema exists, so return values need not be fully specified, yet the description still summarizes the key fields (description, URL, latest report identifier). Combined with the workflow guidance and the annotation coverage, an agent has everything needed to call it correctly.

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?

With zero parameters there is nothing to document, and the description correctly spends no space on inputs, instead describing the shape of each returned item. Baseline for a parameterless tool is 4.

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 and resource (lists all pages Kilotest has tested), naming the domain explicitly, which distinguishes it from siblings like listIssues or listViolators that list other entity types.

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

Usage Guidelines5/5

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

Explicitly prescribes when to call it: 'Use this first to discover whether a page already has any reports before requesting a test,' which positions it before requestNewTest/orderNewTest. That is a concrete workflow rule, not an implied one.

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
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.

Resources