Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

git_log

Read-only

Retrieve recent Git commits from the current repository, with an optional count (1–30), to review history or inspect changes.

Instructions

Read recent commits.

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
countNoNumber of commits, 1..30

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 safety is covered. The description adds nothing beyond that: it doesn't say what "recent" means, whether commits are ordered newest-first, or whether output is truncated.

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?

Four words, front-loaded and waste-free. It is slightly under-specified rather than padded, but there is no filler to cut.

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?

This is a simple single-optional-parameter read tool with full annotations and full schema coverage, so the thin description is nearly sufficient. It still leaves open what "recent" means and how results are ordered or capped, which the agent would want to know.

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?

The single count parameter has 100% schema coverage including a default of 10 and a 1..30 range, so the schema does the work. The description adds no extra meaning beyond it, which is the baseline 3 case.

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?

"Read recent commits" names a specific verb (read) and resource (commits), which distinguishes it from write-side siblings like git_commit and git_stage. It does not differentiate itself from read-side siblings such as git_diff or git_status, so it stops short of a 5.

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 guidance on when to reach for git_log versus git_diff, git_status, or the audit/checkpoint tools. The agent must infer the use case entirely from the name and description.

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