Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_reflog_entry

Read-only

Fetches a single reflog entry by its ID to audit or review design version history changes.

Instructions

Fetch a single reflog entry by id.

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": {
      "reflog_id": "<reflog_id>"
    },
    "name": "get_reflog_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
reflog_idYesThe entry's id, as ``show_reflog`` returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / reflog_id / description
      Added value: +"The entry's id, as ``show_reflog`` returns it."
  2. Addedv1.5.0

TDQS

C2.8/5.0
Behavior2/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 the description needed to add return shape, error behavior for a bad id, or whether reflog entries expire. It adds none of that. Worse, the second sentence is pricing-page boilerplate about Free/Pro/Business/Enterprise tiers that has no bearing on fetching an entry and only introduces confusion about whether access is gated.

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 is irrelevant marketing noise ("Free door, tiered answer — Free: Branch · merge · cherry-pick · undo...") that consumes more space than the actual purpose statement and provides zero operational value.

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?

For a trivial one-parameter read tool with full schema coverage and read-only annotations, the core call requirements are covered. Still missing are any hint about what an entry contains or what happens on an unknown id, and the extraneous tier text detracts from completeness rather than adding to it.

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?

Single parameter with 100% schema description coverage, so the schema already explains reflog_id and even points at show_reflog as the source of ids. The description's "by id" adds nothing beyond that; 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?

The first sentence gives a specific verb and resource ("Fetch a single reflog entry by id") and the singular "a single ... entry" implicitly separates it from the plural sibling show_reflog. However, it never names show_reflog, restore_from_reflog_entry, or any other sibling explicitly, and the trailing tier text muddies rather than sharpens the purpose.

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 when-to-use guidance at all: no statement of when to call this versus show_reflog (listing), restore_from_reflog_entry (mutating), or get_design_version. The only routing hint, that the id comes from show_reflog, lives in the input schema rather than the description.

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