Kilotest

awaitTest

Read-only

Waits for a job ordered via the orderNewTest or orderRetest tool to finish, using the report identifier either tool returned. Use this instead of polling listIssues when an immediate answer is preferred. Blocks until the report is ready, the job fails, or a maximum wait time elapses, sending no interim notices; returns the finished job’s status and, if ready, its report identifier.

Input Schema

Name	Required	Description	Default
`reportID`	Yes	Report identifier returned by orderNewTest or orderRetest (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"
+]
```

Changed6 schema fields changedOct 18, 2026

removedInput schema / properties / jobID

Removed value: -{
-  "description": "Job identifier of the ordered job, from the report identifier returned by orderNewTest (example: x9z)",
-  "type": "string"
-}

addedInput schema / properties / reportID

Added value: +{
+  "description": "Report identifier returned by orderNewTest or orderRetest (example: 260503T0432-x9z)",
+  "type": "string"
+}

removedInput schema / properties / timeStamp

Removed value: -{
-  "description": "Timestamp of the ordered job, from the report identifier returned by orderNewTest, in YYMMDDTHHmm format (example: 260503T0432)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "timeStamp",
-  "jobID"
-]New value: +[
+  "reportID"
+]

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 / details about your wait / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "report identifier": {
-        "$ref": "#/definitions/ReportIdentifier"
-      }
-    },
-    "required": [
-      "report identifier"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "report identifier": {
+        "description": "Identifier of the report, to pass to listIssues once the report is ready (example: 260503T0432-x9z).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "report identifier"
+    ],
+    "type": "object"
+  }
+]

AddedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover read-only and non-destructive behavior, but do not convey that the call blocks. The description adds critical behavior: it blocks until the report is ready, the job fails, or a maximum wait elapses, sends no interim notices, and returns status plus report ID when ready.

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 description is front-loaded with the action and remains compact across two sentences. The alternative routing and blocking caveats each earn their place with no filler.

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?

With annotations and an output schema available, the description covers the essential blocking semantics, alternative, and return behavior. The only meaningful gap is that 'maximum wait time' is mentioned without a duration or default, leaving the blocking window unspecified.

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 reportID is already documented with its source and an example. The description reinforces that the ID comes from orderNewTest or orderRetest, but adds no format or constraint beyond the schema, so the baseline is 3.

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: waits for an ordered job to finish, identified by reportID. It names orderNewTest/orderRetest as the ordering tools and distinguishes the behavior from polling listIssues, making selection unambiguous.

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 this instead of polling listIssues when an immediate answer is preferred. It also ties usage to report IDs returned by orderNewTest or orderRetest, giving clear prerequisite and alternative guidance.

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.