Skip to main content
Glama

Git Log

git_log

Display recent commit history for a Git repository, optionally limiting how many commits are shown.

Instructions

Show recent commit history (git log).

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
max_countNoMaximum number of commits to show.
repo_pathNoPath to the git repository..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden; 'Show' does imply a read-only operation, which is the main behavioral fact an agent needs. Beyond that it says nothing about whether history is truncated, whether it reads only the current branch, or what happens if repo_path is not a git repository.

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

Conciseness4/5

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

A single short sentence, front-loaded with the key action and resource. The parenthetical '(git log)' is mildly redundant but harmless shorthand for the underlying command.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a two-parameter, zero-required read-only tool with a full input schema and an output schema that covers the return shape. The description gives the agent everything needed to decide to call it and how to scope it, so nothing material is missing.

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 coverage is 100%, so both max_count and repo_path are fully documented in the schema and the baseline is 3. The word 'recent' hints that results are limited by default, but the description adds no real meaning beyond the 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?

States a specific verb and resource: 'Show recent commit history', with the underlying command named in parentheses. It is clear enough to separate from git_status and git_diff, though it does not name those siblings explicitly.

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?

Usage is only implied by the phrase 'recent commit history' — an agent can infer this is for reviewing history rather than diffs or working-tree state. There is no explicit when-to-use, when-not-to-use, or routing to git_diff/git_status alternatives.

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