Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

show_reflog

Read-only

List head-mutating operations newest-first to inspect design version history. Filter by branch, artifact, and artifact type, or set a result limit.

Instructions

List head-mutating operations newest-first.

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

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": "show_reflog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe most entries to return, newest first. Default: 100.
branch_idNoOnly entries for this branch. Omitted, every branch.
artifact_idNoOnly entries for this design, preset or feature id. Omitted, every artifact.
artifact_typeNoOnly entries for this kind of branch: ``design``, ``preset`` or ``feature``. Omitted, every kind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / artifact_id / description
      Added value: +"Only entries for this design, preset or feature id. Omitted, every artifact."
    • addedInput schema / properties / artifact_type / description
      Added value: +"Only entries for this kind of branch: ``design``, ``preset`` or ``feature``.  Omitted, every kind."
    • addedInput schema / properties / branch_id / description
      Added value: +"Only entries for this branch.  Omitted, every branch."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 100."New value: +"The most entries to return, newest first. Default: 100."
  2. Addedv1.5.0

TDQS

C2.9/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, so safety is covered and the bar is lower. The tier sentence does add genuinely useful behavior context in principle — results appear plan-gated (Free limited to designs you keep) — but it is written as garbled ad copy ("Free door, tiered answer") with no explanation of how a Free-tier limit manifests in the returned list. Nothing is said about ordering guarantees beyond "newest-first" or what a reflog entry contains.

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

Conciseness2/5

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

The first sentence is tight and front-loaded, but the second sentence is a run-on pricing block ("Free · Pro · Business: ✓ · Enterprise: ✓") that reads as pasted marketing text and obscures more than it conveys. Roughly half the description does not earn its place as tool guidance.

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?

It is a read-only, zero-required-parameter listing tool with full schema coverage and no output schema, so the essentials are covered. However, the description leaves the agent guessing about the shape of results, the meaning of "head-mutating" for this domain, and how tier gating affects what comes back.

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 limit, branch_id, artifact_id and artifact_type are all documented in the schema with defaults and omission semantics. The description adds no meaning beyond that, which puts it at the baseline for a fully documented schema.

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?

"List head-mutating operations newest-first" gives a concrete verb (list) and a materially specific resource (head-mutating operations, i.e. reflog entries) with ordering. It is clear enough to act on, but it never distinguishes this from closely related siblings such as get_reflog_entry, restore_from_reflog_entry, or show_branch_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no stated when-to-use or when-not-to-use guidance, and no pointer to siblings like get_reflog_entry for a single entry or restore_from_reflog_entry for acting on one. The second sentence is plan/tier marketing copy rather than invocation guidance, so it does not help the agent decide to call this tool.

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