Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_bisect_sessions

Read-only

List active bisect sessions, optionally filtered by artifact type (design, preset, or feature), to track in-progress version graph comparisons in Kiln Pro.

Instructions

List active bisect sessions, optionally filtered by artifact type (design / preset / feature).

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bisect_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_typeNoOnly sessions over this kind of version graph: ``design``, ``preset`` or ``feature``. Omitted, every active session; any other word is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / artifact_type / description
      Added value: +"Only sessions over this kind of version graph: ``design``, ``preset`` or ``feature``.  Omitted, every active session; any other word is refused."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond the annotations: only *active* sessions are returned and a Kiln Pro entitlement is required. It stops short of noting whether it paginates or how many sessions could come back.

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 with zero filler; the core action is front-loaded and the filter requirement follows immediately. The trailing "Needs Kiln Pro." fragment is terse but reads as an afterthought rather than an integrated prerequisite.

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 single optional parameter, read-only tool with no output schema, the definition covers purpose, filtering scope, and the Kiln Pro gate. The remaining gap (return shape, plausibly empty result behavior) is minor given the annotations already establish it as a safe read.

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 spells out the three permitted values plus the refuse-unknown-words rule. The description merely restates the same enum in the parenthetical, adding no new meaning beyond the schema, so baseline 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?

Specific verb+resource: "List active bisect sessions" with an explicit optional filter over design/preset/feature. An agent can distinguish this from the bisect_start/bisect_good/bisect_bad siblings by the verb alone, though the description never names those siblings to reinforce the split.

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?

Usage is implied by "active" sessions and the filter parameter, and the "Needs Kiln Pro" line flags an entitlement prerequisite. However, there is no explicit statement of when to call this versus the other bisect_* tools (e.g. before bisect_end to see what is open), so an agent must infer the workflow position.

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