Skip to main content
Glama

Kilotest

by com.kilotest
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
reportIDYesReport identifier returned by orderNewTest or orderRetest (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 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"
+  }
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive), and the description adds behavior they cannot express: the call blocks, it terminates on ready/failure/timeout, it emits no interim notices, and it returns status plus a report identifier when ready. That is exactly the context an agent needs before committing to a blocking call.

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 tight sentences, front-loaded with the action and the input's origin, then the alternative, then the blocking semantics. No filler or restatement of the name.

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?

With an output schema present, return values need not be detailed, and the description still summarizes the return shape. Blocking, timeout, and failure termination are all disclosed, leaving nothing an agent needs missing.

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 the single property already documents its provenance and format example, so the description's 'using the report identifier either tool returned' largely repeats structured data. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names a specific verb and resource ('waits for a job ordered via orderNewTest or orderRetest to finish') and ties the input to the identifier those tools return. It is immediately distinguishable from read-only siblings like listIssues or getReport.

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?

It explicitly routes the agent: 'Use this instead of polling listIssues when an immediate answer is preferred,' naming both the alternative and the condition that selects this tool. No inference is required.

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