Kilotest

requestRetest

Submits a request to retest a page whose existing report is considered obsolete; queued for manager approval. Use orderRetest instead for immediate, automatically approved retesting. Returns a request confirmation with disposition details.

Input Schema

Name	Required	Description	Default
`reason`	Yes	20- to 100-character reason why the page should be retested
`reportID`	Yes	Identifier of the latest report about the page (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.

Changed5 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"
+}
```
- 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"
+]
```

Changed4 schema fields changedOct 18, 2026

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"
+]

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

addedOutput schema / properties / response content / properties / disposition of your request

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "how a web user can check for completion": {
+          "type": "string"
+        },
+        "how you can check for completion": {
+          "type": "string"
+        },
+        "what happens next": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "what happens next",
+        "how you can check for completion",
+        "how a web user can check for completion"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / response content / required

Previous value: -[
-  "details about your request"
-]New value: +[
+  "details about your request",
+  "disposition of your request"
+]

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare this is not read-only, not idempotent, and not destructive. The description adds meaningful workflow context beyond annotations: the request is queued for manager approval and returns a confirmation with disposition details. It does not cover auth or rate-limit behavior, but the approval queue is the key behavioral trait.

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?

The core purpose and approval-queue behavior are front-loaded, followed by the alternative tool in the next sentence. There is no redundant or filler text.

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?

The tool is a request-style mutation with annotations and an output schema. The description covers the queueing behavior, the alternative sibling, and the return confirmation, which is sufficient for an agent to call it correctly.

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 required parameters are clearly documented in the schema. The description does not add syntax or constraints beyond the schema, so the baseline score of 3 is appropriate when the schema carries parameter semantics.

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: submits a retest request for a page whose existing report is obsolete. It also explicitly distinguishes itself from orderRetest, so an agent can differentiate it from the sibling without inspecting 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 to use orderRetest instead for immediate, automatically approved retesting, which identifies the alternative and the condition that selects it. The queued-for-manager-approval detail also makes clear when this tool is appropriate.

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.