Kilotest

requestFeature

Requests a new feature or an improvement to an existing one. Requires a feature parameter describing the requested feature or improvement. If you want to question a diagnosis, call questionDiagnosis instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feature": "<feature>"
    },
    "name": "requestFeature"
  }
}

Input Schema

Name	Required	Description	Default
`feature`	Yes	20- to 1000-character proposal for a new feature or a feature improvement, evaluated by the reviewing manager

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.

Changed6 schema fields changedNov 7, 2026

changedInput schema / properties / feature / description

Previous value: -"20- to 1000-character description of requested feature improvement or new feature"New value: +"20- to 1000-character proposal for a new feature or a feature improvement, evaluated by the reviewing manager"

addedInput schema / properties / feature / maxLength
```
Added value: +1000
```
addedInput schema / properties / feature / minLength
```
Added value: +20
```

changedOutput schema / properties / this request / properties / body / properties / feature / description

Previous value: -"20- to 1000-character description of requested feature improvement or new feature"New value: +"20- to 1000-character proposal for a new feature or a feature improvement, evaluated by the reviewing manager"

addedOutput schema / properties / this request / properties / body / properties / feature / maxLength
```
Added value: +1000
```
addedOutput schema / properties / this request / properties / body / properties / feature / minLength
```
Added value: +20
```

Changed5 schema fields changedOct 30, 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 2, 2026
- removedOutput schema / definitions / RequestReference / properties / method / const
```
Removed value: -"GET"
```
- addedOutput schema / definitions / RequestReference / properties / method / enum
```
Added value: +[
+  "GET",
+  "POST"
+]
```

Changed2 schema fields changedSep 20, 2026

changedInput schema / properties / feature / description

Previous value: -"description of requested feature improvement or new feature"New value: +"20- to 1000-character description of requested feature improvement or new feature"

changedOutput schema / properties / this request / properties / body / properties / feature / description

Previous value: -"description of requested feature improvement or new feature"New value: +"20- to 1000-character description of requested feature improvement or new feature"

First observedSep 1, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds context that the proposal is reviewed, but does not disclose what happens on submission (ticket creation, who is notified, whether duplicates are accepted) or the non-idempotent behavior implied by the annotations.

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?

Three short sentences, front-loaded with the core action and ending with the alternative-tool rule. The middle sentence partially restates the name ('Requires a feature parameter describing the requested feature'), which is mild redundancy but not damaging.

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?

The tool is simple (one param, output schema present), and the description plus annotations cover what an agent needs to call it correctly. Only the post-submission outcome is left implicit, which is a minor gap for a non-idempotent write action.

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 parameter is fully documented in-schema, including length bounds and the evaluation context. The description only restates that the feature parameter is required and what it should describe, adding essentially no meaning beyond the schema.

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 ('Requests a new feature or an improvement to an existing one') and explicitly distinguishes itself from the sibling questionDiagnosis. An agent can identify the action without opening the schema.

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?

Gives an explicit exclusion with a named alternative: 'If you want to question a diagnosis, call questionDiagnosis instead.' It does not cover other plausible near-neighbors such as requestNewTest or requestRetest, but the routing rule it does give 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

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

Need Help?