Skip to main content
Glama

Git Commit

git_commit

Commit staged changes to a Git repository using a custom message and optional repository path.

Instructions

Commit staged changes with a message (git commit).

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_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoCommit message.update
repo_pathNoPath to the git repository..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. For a mutating git operation it says nothing about what happens when nothing is staged, whether hooks run, whether the commit is reversible, whether it requires a clean working tree, or what errors surface — only that a message is supplied.

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 front-loaded sentence with zero redundancy and the key constraint ("staged changes") placed before the parenthetical. It is efficient, though the brevity borders on under-specification rather than tightness.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the tool is a mutating VCS operation with no annotations and many near-identical siblings. Given that complexity, the description omits the staging prerequisite detail, failure modes, and sibling routing an agent needs to call it correctly.

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 parameters (message, repo_path) documented and defaulted in the schema, so baseline is 3. The description adds no meaning beyond it — it doesn't explain the default message "update" or when to override repo_path.

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 ("Commit staged changes with a message") and even maps it to the underlying git command, so the action is unambiguous. It does not, however, distinguish itself from siblings such as commit_changes or prepare_commit, which an agent must choose between.

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?

The word "staged" implies a prerequisite (changes must already be staged via git_add), which is a weak usage hint. There is no explicit when-to-use or when-not-to-use guidance and no mention of the very similar commit_changes or prepare_commit tools.

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