Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

bisect_end

Destructive

End a bisect session early without requiring full convergence, using the session ID returned at start. Requires Kiln Pro.

Instructions

End a bisect session without requiring full convergence.

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_end"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe bisect session's id, as ``bisect_start`` or ``list_bisect_sessions`` returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds that convergence is not required, signaling that partial bisect work may be abandoned, and it discloses the Kiln Pro entitlement requirement. It stops short of explaining whether the session is deleted or recoverable.

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 two short sentences, front-loading the action and then the prerequisite. There is no redundant or filler wording.

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?

For a one-parameter destructive tool with a fully documented schema and annotations covering safety, the description supplies purpose, early-termination behavior, and entitlement. It could additionally state what happens to the session state, but it is complete enough to invoke 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?

There is only one parameter, and schema description coverage is 100%, with session_id already documented as coming from bisect_start or list_bisect_sessions. The description adds no further syntax or constraints beyond the schema, 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 states a specific verb and resource: 'End a bisect session.' The clause 'without requiring full convergence' clarifies the special scope of this end operation. It does not name a sibling alternative, but the purpose is clear enough to distinguish it from starting or advancing a bisect.

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?

The phrase 'without requiring full convergence' tells the agent this tool is for terminating a bisect early, and 'Needs Kiln Pro' states a prerequisite. It provides clear usage context but does not explicitly name alternatives or when not to use it.

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