Skip to main content
Glama

Commit Changes

commit_changes

Stage all workspace changes and commit them to Git using the approved commit message.

Instructions

Stage all workspace changes and commit them to Git with the approved commit message.

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": {
      "message": "<message>"
    },
    "name": "commit_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
messageYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose one meaningful trait — that it stages ALL workspace changes rather than a selected subset — but says nothing about irreversibility, whether hooks run, what happens on failure or an empty working tree, or whether it can be undone. For an unannotated mutation tool that is a serious gap.

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?

One sentence, front-loaded with the action and scope, with no filler. It is efficient, though the brevity is part of why the alternatives and path semantics go unaddressed.

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?

An output schema exists, so return values needn't be explained, and that lowers the bar. Still, for a Git mutation tool with an undocumented path parameter and three near-duplicate siblings, the definition leaves an agent short of what it needs to call this correctly and only this.

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 0%, so the description must compensate, and it only partly does: 'approved commit message' adds context for the message parameter, but the path parameter (whose purpose and default of '.' are undocumented anywhere) is never addressed. Half the surface is unexplained.

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 compound verb (stage + commit) against a specific resource (workspace changes to Git), so the effect is unmistakable. It loses a point because it never distinguishes itself from the closely overlapping siblings git_add, git_commit, and prepare_commit, leaving the agent to guess whether this is a higher-level wrapper or a duplicate.

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?

The phrase 'approved commit message' implicitly signals a gated workflow (prepare/approve, then commit), which is useful context. But there is no explicit when-to-use versus git_add/git_commit, no statement that changes should already be reviewed, and no exclusions — the agent must infer the routing.

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