Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

bisect_skip

Skip an uncertain or untested candidate in a bisect session to continue narrowing the revision range without marking it pass or fail.

Instructions

Skip the current candidate (uncertain / untested).

Needs Kiln Pro.

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": {
      "session_id": "<session_id>"
    },
    "name": "bisect_skip"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe bisect session's id, as ``bisect_start`` or ``list_bisect_sessions`` returned it.
version_idNoThe version to skip. Omitted, the session's current candidate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / session_id / description
      Added value: +"The bisect session's id, as ``bisect_start`` or ``list_bisect_sessions`` returned it."
    • addedInput schema / properties / version_id / description
      Added value: +"The version to skip.  Omitted, the session's current candidate."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description usefully adds the 'Needs Kiln Pro' entitlement gate, which annotations cannot express. It does not say what skipping does to the session state, whether it is reversible, or whether the candidate is excluded from future rounds — meaningful gaps for a bisect workflow.

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?

Two short lines, front-loaded with the action and its condition; no wasted words. The 'Needs Kiln Pro' prerequisite is separated but would read better folded into the same sentence.

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?

The tool is simple and the parameters are fully documented, but with no output schema the description should say what a skip returns or how the session advances. For a step in a multi-tool bisect workflow, that omission leaves the agent guessing about the next move.

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% and the schema already explains that omitting version_id targets the session's current candidate. The description adds nothing 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.

Purpose4/5

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

The description gives a specific verb ('Skip') plus the target ('the current candidate') and qualifies it as 'uncertain / untested', which implicitly separates it from bisect_good and bisect_bad. It does not name those siblings outright, so an agent must infer the distinction from their names rather than from this text.

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?

'Uncertain / untested' states the condition under which skipping applies, which is real usage guidance. However, it never names the alternatives (bisect_good, bisect_bad, bisect_current) or says when skipping is wrong, leaving the branch-selection decision implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools