Skip to main content
Glama

Kilotest

by io.github.jrpool
OverviewDiscussionsAdmin

requestTest

Process my request to test a page about which no report is available yet.

Input Schema

TableJSON 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 listReports output

Output Schema

TableJSON 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
    • changedInput schema / properties / description / description
      Previous value: -"10- 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 listReports output"
    • changedOutput schema / properties / this request / properties / body / properties / description / description
      Previous value: -"10- 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 listReports output"
  2. 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"
+]
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations only indicate this is not read-only, not idempotent, and not destructive; the description adds no side-effect information such as whether a test is immediately triggered, whether a report is created, or whether the operation is asynchronous. Since annotations are minimal, the description carries the burden and does not satisfy it.

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?

The description is a single, compact sentence that is easy to parse. The phrase 'Process my request' is slightly filler-heavy and could be replaced with a more direct verb, but overall it is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and fully documented parameters, the description supplies the core purpose and the key condition of no existing report. However, it does not clarify when to choose this over requestRetest or requestFeature, nor what side effects the 'processing' entails, leaving notable gaps.

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%, so all three parameters are already documented with types and length constraints. The description adds only the contextual hint that the page should lack a report, which is enough given the schema already explains each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly indicates the tool handles requests to test a page that has no report yet, which distinguishes it from sibling requestRetest. However, 'Process my request' is somewhat indirect and does not explicitly state whether it creates a task, queues a test, or produces a report.

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

Usage Guidelines3/5

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

The phrase 'about which no report is available yet' implies this tool is for untested pages, giving useful contextual guidance. But it does not explicitly name alternatives like requestRetest or mention when not to use this tool, leaving usage boundaries mostly implicit.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources