Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

push_reflog_to_cloud

Mirror local reflog entries to your tenant's cloud reflog, newest first, with optional limits or branch-type filtering. Requires Kiln Pro to sync version history off-device.

Instructions

Mirror local reflog entries up to the tenant's cloud reflog.

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

Input Schema

NameRequiredDescriptionDefault
limitNoThe most local entries to push, newest first. Default: 500.
artifact_typeNoOnly push entries for this kind of branch: ``design``, ``preset`` or ``feature``. Omitted, every kind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / artifact_type / description
      Added value: +"Only push entries for this kind of branch: ``design``, ``preset`` or ``feature``.  Omitted, every kind."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 500."New value: +"The most local entries to push, newest first. Default: 500."
  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 a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds the Kiln Pro entitlement requirement, which is real added context, but says nothing about idempotency, whether remote entries can be overwritten or duplicated, or what happens on a partial/rate-limited push. For a cloud-mutating tool that is a meaningful gap.

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?

Two short lines: the action and direction are front-loaded, and the prerequisite follows immediately. There is no filler or redundant restatement of the name.

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?

With only two optional parameters, full schema documentation, and annotations covering the safety profile, the core is adequate. What is missing is any hint of return/confirmation behavior or failure semantics for a write that reaches a tenant cloud store, which matters since there is no output schema.

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%, with both `limit` (default 500, newest first) and `artifact_type` (design/preset/feature enum values) fully documented in the schema. The description adds no meaning beyond that, so the 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?

"Mirror local reflog entries up to the tenant's cloud reflog" gives a specific verb (mirror), a specific resource (reflog entries) and an explicit direction (local -> cloud), which distinguishes it from the pull/cloud-sync siblings without naming them. It stops short of naming an alternative tool outright, so it is clear but not fully self-differentiating.

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?

"Needs Kiln Pro" is a genuinely useful eligibility prerequisite. However, there is no statement of when to prefer this over pull_reflog_from_cloud, cloud_sync_now, or cloud_push_branch, and no guidance about how often or in what workflow the push should be triggered.

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