Skip to main content
Glama

Kilotest

by com.kilotest
OverviewDiscussionsAdmin

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

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. Changed4 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"
+]
  2. Changed2 schema fields changed
    • removedOutput schema / definitions / RequestReference / properties / method / const
      Removed value: -"GET"
    • addedOutput schema / definitions / RequestReference / properties / method / enum
      Added value: +[
+  "GET",
+  "POST"
+]
  3. Changed2 schema fields changed
    • 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"
+]
  4. First observed

TDQS

A4.5/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, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the call only queues a request pending manager approval rather than executing the retest, and it returns a confirmation with disposition details. It could go further on rate limits or what happens if a request is rejected, but the approval-gating disclosure is the key information.

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 short sentences with zero waste: the core action and its approval gating come first, the sibling routing second, the return behavior last. Every sentence earns its place.

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, so return shape needn't be detailed, yet the description still flags the confirmation/disposition response. For a two-parameter, approval-gated mutation tool, an agent has everything needed to decide between this and orderRetest and 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%, with both reportID and the 20–100 character reason constraint fully documented in the schema. The description adds nothing about parameters beyond that, so the baseline of 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 ('Submits a request to retest a page') plus the qualifying condition (existing report obsolete) and the downstream behavior (queued for manager approval). It explicitly names the sibling it is not (orderRetest), so an agent can distinguish the two without opening a 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?

Names the alternative tool explicitly and the condition that selects it: use orderRetest when you want immediate, automatically approved retesting; use this when the report is obsolete and approval is acceptable. This is the when/when-not/alternatives pattern executed cleanly.

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
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources