Skip to main content
Glama

commit_progress

Create a git commit of current progress to checkpoint completed features and safely resume multi-hour autonomous coding sessions.

Instructions

Create a git commit with the current progress. Use after completing features to checkpoint work.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectDir": "<projectDir>",
      "message": "<message>"
    },
    "name": "commit_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesCommit message describing the progress
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a write operation. It never says which files are staged or whether the tool stages them itself, what happens on a dirty tree or a failed commit, whether the commit is reversible, or what the call returns.

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 short sentences, no filler, and the core action is front-loaded ahead of the usage hint. Nothing is redundant or buried.

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?

The tool is simple (two required string params, no output schema), so the description is minimally sufficient. For an unannotated mutation, though, it should say what gets committed and what the agent receives back on success or failure.

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 message and projectDir documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond that, such as message conventions or path requirements.

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 ('Create a git commit') with the scope 'current progress', which is clear enough for an agent to identify the operation. It does not, however, distinguish itself from related siblings such as get_progress_log, so it stops short of the top mark.

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?

'Use after completing features to checkpoint work' gives a clear trigger condition for invocation. There are no explicit exclusions or named alternatives for cases where an agent might want to inspect progress instead of committing it.

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