Skip to main content
Glama

Show the version history of the working copy

patchwork_log
Read-onlyIdempotent

Lists each working-copy version oldest first with timestamps, messages, and up to 10 changes, so you can review edit history or count undo calls needed to reach a version.

Instructions

List every version of the working copy, oldest first, with its time, its message and up to 10 of its changes. Use it to review what was done, or to count how many patchwork_undo calls lead back to a version. For the current version only, use patchwork_status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered structurally. The description adds genuinely non-inferable behavior: chronological ordering and a cap of 10 changes per version, which signals truncated results. It stops short of saying whether paging or a total count is available when a version has more than 10 changes.

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 sentences, no filler: the first defines the operation and its output, the second covers use cases and the sibling alternative. Ordering and the 10-change cap are front-loaded where the agent will read them.

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?

With no output schema, the description carries the return-shape burden and largely discharges it by naming time, message and changes. The one gap is the counting use case it recommends: it never says whether the total number of versions is reported or must be derived from a truncated list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4 and no schema explanation is needed. The description correctly adds no parameter detail and instead spends its words on output shape and sibling routing.

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?

States a specific verb and resource ('List every version of the working copy') plus ordering ('oldest first') and returned fields ('time, message, up to 10 of its changes'). It also contrasts explicitly with patchwork_status for the current-version case, so an agent can separate it from siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives two concrete use cases (reviewing what was done, counting patchwork_undo calls back to a version) and an explicit exclusion routing to patchwork_status for current state. When-to-use and when-not-to-use are both present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.