Skip to main content
Glama

Kilotest

by com.kilotest
OverviewDiscussionsAdmin

orderRetest

Orders a retest of a page whose existing report is considered obsolete, with automated approval or rejection and immediate enqueuing if approved. Use this instead of requestRetest when immediate retesting is wanted; testing typically takes 2 to 4 minutes. Returns an order confirmation and disposition details, including, if approved, a report identifier and a question about whether to wait for completion with the awaitTest tool.

Input Schema

NameRequiredDescriptionDefault
reasonYes20- to 100-character reason why the page should be retested
reportIDYesIdentifier of the latest report about the page (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 latest report about the page (example: x9z)",
-  "type": "string"
-}
    • addedInput schema / properties / reportID
      Added value: +{
+  "description": "Identifier of the latest report about the page (example: 260503T0432-x9z)",
+  "type": "string"
+}
    • removedInput schema / properties / timeStamp
      Removed value: -{
-  "description": "Timestamp of the latest report about the page in YYMMDDTHHmm format (example: 260503T0432)",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "timeStamp",
-  "jobID",
-  "reason"
-]New value: +[
+  "reportID",
+  "reason"
+]
    • removedOutput schema / definitions / ReportIdentifier
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "jobID": {
-      "description": "Job identifier to pass to listIssues once the report is ready.",
-      "type": "string"
-    },
-    "timeStamp": {
-      "description": "Timestamp to pass to listIssues once the report is ready.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "timeStamp",
-    "jobID"
-  ],
-  "type": "object"
-}
    • changedOutput schema / properties / response content / properties / disposition of your order / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "do you want to wait for completion": {
-        "type": "string"
-      },
-      "how you can check for completion": {
-        "type": "string"
-      },
-      "report identifier": {
-        "anyOf": [
-          {
-            "$ref": "#/definitions/ReportIdentifier"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "what happens next": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "what happens next",
-      "report identifier",
-      "how you can check for completion",
-      "do you want to wait for completion"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "do you want to wait for completion": {
+        "type": "string"
+      },
+      "how you can check for completion": {
+        "type": "string"
+      },
+      "report identifier": {
+        "anyOf": [
+          {
+            "description": "Identifier of the report, to pass to listIssues once the report is ready (example: 260503T0432-x9z).",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "what happens next": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "what happens next",
+      "report identifier",
+      "how you can check for completion",
+      "do you want to wait for completion"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, and the description adds genuinely new context: the request goes through an automated approval/rejection gate, enqueuing only happens if approved, and typical latency is 2-4 minutes. It does not mention quota/credit consumption or what happens to the superseded report, which would be the remaining gap for a mutating tool.

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?

Front-loaded with purpose, then the alternative-routing guidance, then the return summary. The final clause about "a question about whether to wait for completion with the awaitTest tool" is slightly convoluted, but every sentence carries information.

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, yet the description still usefully sketches the return shape (order confirmation, disposition, report identifier on approval). Combined with the explicit timing and the awaitTest handoff, an agent has everything needed to call this correctly and know what to do next.

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 both parameters are fully documented in the schema (reason length bounds, reportID format and example). The description adds only the framing that the report should be about the obsolete page, no additional format or validation detail, so the 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 and resource ("Orders a retest of a page") plus the precondition ("whose existing report is considered obsolete") and the outcome ("automated approval or rejection and immediate enqueuing if approved"). It also names the sibling it is not, requestRetest, so an agent can distinguish the two without reading 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 Guidelines5/5

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

Explicitly says "Use this instead of requestRetest when immediate retesting is wanted," giving both the alternative and the selecting condition. It further routes the agent to awaitTest for the wait-for-completion case, and sets an expectation of 2-4 minutes.

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