Skip to main content
Glama

git_log

Read-only

List recent commits in a place's mirror repo (newest first: short hash, date, message); read-only, notes when none exist. Use returned refs with git_show, git_diff, git_restore, or git_revert.

Instructions

List recent commits in a place's mirror repo, newest first: short hash, date and message. Read-only; says so when there are no commits yet. Use it to find the ref for git_show, git_diff, git_restore or git_revert.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many commits to list. Default 20.
placeNoTarget place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / count / description
      Added value: +"How many commits to list. Default 20."
    • addedInput schema / properties / count / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / count / minimum
      Added value: +1
    • changedInput schema / properties / count / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / place / description
      Previous value: -"Target place (PlaceId or project name); defaults to the bound/sole place"New value: +"Target place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'Read-only' adds no new safety information. The description does add behavior beyond the annotations: newest-first ordering, the exact fields returned, and the empty-state response ('says so when there are no commits yet'), which prevents an agent from mistaking an empty log for an error.

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, front-loaded with the core action and output shape, followed by the routing hint. No filler or restatement of the title.

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 burden of describing return values and does so (hash, date, message; ordered newest first; explicit empty-state message). Only the pagination/truncation behavior when 'count' is large is unaddressed, a minor gap for a two-parameter read tool.

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 'count' (default 20) and 'place' (PlaceId or project name, defaults to the bound place) fully documented in the schema. The description only alludes to the target repo via 'a place's mirror repo' and adds no new detail about count limits or default resolution, so baseline 3 applies.

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 recent commits in a place's mirror repo') plus ordering ('newest first') and the returned fields ('short hash, date and message'). The closing sentence distinguishes it from git_show/git_diff/git_restore/git_revert by framing this tool as the ref-discovery step preceding them.

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

Usage Guidelines4/5

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

Gives an explicit use case ('Use it to find the ref for git_show, git_diff, git_restore or git_revert'), which routes the agent well against siblings that require a ref. It stops short of any when-not guidance, e.g. that git_status is the choice for working-tree state rather than history.

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