Kilotest

requestNewTest

Submits a request to test a page that has no report yet; queued for manager approval. Use orderNewTest instead for immediate, automatically approved testing. Returns a request confirmation with disposition details.

Input Schema

Name	Required	Description
`URL`	Yes	12- to 300-character URL of the page, including the https:// scheme and any query
`reason`	Yes	20- to 100-character reason why the page should be tested
`description`	Yes	1- to 100-character description of the page conforming to the naming convention used in the listPages output

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"
+]
```

Changed2 schema fields changedOct 10, 2026

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"

AddedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already disclose that this is not read-only, is open-world, not idempotent, and not destructive. The description adds meaningful behavior beyond the annotations: requests are queued for manager approval and return a confirmation with disposition details. It does not explain rejection/failure handling, but the core workflow is clear.

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 three tight sentences: purpose first, alternative second, return behavior third. Every sentence adds decision-relevant information and there is no repetition or filler.

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?

Given the rich annotations, complete input schema, and presence of an output schema, the description supplies the key missing context: the manager-approval queue and the contrast with orderNewTest. An agent has enough information to select and invoke this tool 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%, so the three parameters and their constraints are fully documented in the schema. The description does not add parameter-level meaning beyond the schema, which is acceptable at the baseline for complete schema coverage.

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 states a specific verb and resource: submitting a request to test a page that has no report yet. It also distinguishes this tool from the sibling orderNewTest by explaining the approval-queue behavior versus immediate automatically approved testing.

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 gives an explicit condition for use—pages with no report yet—and names the alternative orderNewTest for immediate, automatically approved testing. The routing decision between the two tools is unambiguous.

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.