Skip to main content
Glama

git_commit

Commit staged changes in a Git repository using a specified message and optional working directory path.

Instructions

Commit staged changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesCommit message
cwdNoRepository path

Implementation Reference

  • Core handler for the 'git_commit' tool. Executes 'git commit -m <message>' via gitCommand and validates the 'message' argument is present.
    async gitCommit(args: GitCommitArgs): Promise<ToolResult> {
      const { message, cwd } = args;
      ValidationUtils.validateRequired({ message }, ['message']);
      return await this.gitCommand(['commit', '-m', message], cwd);
    }
  • Type definition GitCommitArgs interface: extends GitCommandArgs with required 'message' string property.
    export interface GitCommitArgs extends GitCommandArgs {
      message: string;
    }
  • src/index.ts:191-192 (registration)
    Routes the 'git_commit' tool name to GitService.gitCommit() in the main handler switch statement.
    case 'git_commit':
      return await this.gitService.gitCommit(args as GitCommitArgs);
  • Input schema definition for 'git_commit' tool: requires 'message' string, optional 'cwd' string.
    {
      name: 'git_commit',
      description: 'Commit staged changes',
      inputSchema: {
        type: 'object',
        properties: {
          message: { type: 'string', description: 'Commit message' },
          cwd: { type: 'string', description: 'Repository path' },
        },
        required: ['message'],
      },
    },
  • GitCommit interface in types.ts: defines the shape of a commit object (hash, author, date, message).
    export interface GitCommit {
      hash: string;
      author: string;
      date: string;
      message: string;
    }
Behavior2/5

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

No annotations provided, and description only says 'Commit staged changes'. Lacks disclosure of auth needs, side effects, or error conditions. Could be considered a tautology.

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?

Extremely concise (three words) and front-loaded. However, some may argue it underspecifies, but it is not verbose.

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?

For a simple tool, the description conveys the core action, but lacks output format, failure modes, or usage hints. Adequate but not comprehensive.

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% with clear parameter descriptions. Description adds no extra meaning beyond the schema, so baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'Commit' and resource 'staged changes', distinguishing it from sibling tools like git_add (stages) and git_push (pushes commits).

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?

No guidance on when to use or avoid this tool. No mention of prerequisites like staged changes being required, nor alternatives when changes are not staged.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentics-ai/code-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server