Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

show_branch_history

Read-only

List commits on a single branch newest-first, with optional print-outcome counts and success rates, to review design history in text mode.

Instructions

List the commits on a single branch, newest-first — the text-mode companion to visualize_branch_tree.

Free door, tiered answer — Free: Branch · merge · cherry-pick · undo, on the designs you keep · Pro: Branch · merge · cherry-pick · undo, on every design · Business: ✓ · Enterprise: ✓.

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": {
      "design_id": "<design_id>",
      "branch_name": "<branch_name>"
    },
    "name": "show_branch_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNewest-N cap. Default 50; pass 0 for no cap. Default: 50.
design_idYesTarget design.
branch_nameYesName of the branch to walk. Case-sensitive.
annotate_outcomesNoWhen ``True`` (default), join each commit against the print-outcome tracker and include ``outcome_count`` + ``success_rate`` in the row. Skip the join when you only need change summaries and want the tool to run faster. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / annotate_outcomes / description
      Previous value: -"Default: true."New value: +"When ``True`` (default), join each commit against the print-outcome tracker and include ``outcome_count`` + ``success_rate`` in the row. Skip the join when you only need change summaries and want the tool to run faster. Default: true."
    • addedInput schema / properties / branch_name / description
      Added value: +"Name of the branch to walk.  Case-sensitive."
    • addedInput schema / properties / design_id / description
      Added value: +"Target design."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 50."New value: +"Newest-N cap.  Default 50; pass 0 for no cap. Default: 50."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful ordering and single-branch scope, but it does not disclose error behavior, return structure, or pagination behavior beyond what the schema implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is clear, front-loaded, and relevant. The second sentence about free/pro/business/enterprise tiers is confusing, marketing-like, and not actionable for an agent invoking the tool, which dilutes the definition.

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 simple read-only listing tool, the description provides enough context to understand what is returned: commits on a branch, newest-first. It could say more about commit row contents, but the schema documents annotate_outcomes and limit, and annotations cover the safety profile.

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 all four parameters are already documented in the schema. The description adds no parameter-specific meaning beyond reinforcing branch scope and newest-first ordering, so the baseline score of 3 is appropriate.

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 first sentence states a specific verb and resource: list commits on a single branch, newest-first. It also names the sibling visualizer as a companion, which helps distinguish text-mode listing from visual tree exploration.

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?

The description gives implied usage by calling this the text-mode companion to visualize_branch_tree. However, it does not explicitly say when to use this versus other branch-related tools such as compare_branches, list_design_branches, or show_design_lineage, and it provides no exclusions.

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