Skip to main content
Glama

Kilotest

by com.kilotest
OverviewDiscussionsAdmin

orderNewTest

Orders testing of a page that has no report yet, with automated approval or rejection and immediate enqueueing if approved. Use this instead of requestNewTest when immediate testing 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
URLYes12- to 300-character URL of the page, including the https:// scheme and any query
reasonYes20- to 100-character reason why the page should be tested
descriptionYes1- to 100-character description of the page conforming to the naming convention used in the listPages output

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. Changed2 schema fields changed
    • 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. Changed2 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"1- to 100-character description of the page conforming to the naming convention used in the listReports output"New value: +"1- to 100-character description of the page conforming to the naming convention used in the listPages output"
    • changedOutput schema / properties / this request / properties / body / properties / description / description
      Previous value: -"1- to 100-character description of the page conforming to the naming convention used in the listReports output"New value: +"1- to 100-character description of the page conforming to the naming convention used in the listPages output"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the request may be auto-rejected, approval means immediate enqueueing, and a run takes 2-4 minutes. Annotations already cover readOnly/destructive/openWorld, so the remaining gap (auth requirements, quota/cost of ordering, what rejection returns) is modest.

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-loads the core action in the first clause and keeps to two sentences with no filler. The second sentence is dense, stacking return contents, timing, and the awaitTest hand-off into one long construction, but nothing is wasted.

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?

Covers precondition, alternatives, latency expectations, and outcome shape for a non-idempotent write tool whose output schema exists. Minor omissions are what happens on rejection and whether re-invocation creates a duplicate order, but an agent has enough 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 coverage is 100%, with character limits and URL/description conventions documented in the schema itself. The description adds no parameter-level meaning (e.g., why a reason is required, what naming convention listPages uses), 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 testing of a page) plus the key precondition (page has no report yet), which separates it from orderRetest. The automated approval/rejection and immediate enqueueing behavior further pins down what the call actually does.

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

Usage Guidelines4/5

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

Explicitly routes the agent: 'Use this instead of requestNewTest when immediate testing is wanted', and points to awaitTest for waiting. It also implies the page must have no prior report, though it never names orderRetest as the path for pages that already have one, leaving that exclusion to inference.

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