Skip to main content
Glama
Repository Manager

Repository Manager

Commit Code

rm_git_commit_code

Commit code changes across one or more Git repositories using typed bulk operations, with optional pre-commit hooks and no arbitrary host commands.

Instructions

Commit code (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

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": "rm_git_commit_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath to execute in.
job_idNoBackground rm_git job id; required for action='status' or 'cancel'.
commandNoThe Git command to execute for 'raw' action (e.g., 'git status')
messageNoCommit message for 'commit' / 'commit_code' actions.
summaryNoFor action='status': return compact progress by default; false includes full detail.
threadsNoParallel workers for bulk operations.
projectsNoOptional comma-separated list of repository URLs to clone or directory names/paths to pull/push/add/commit.
run_precommitNoFor 'commit_code': run pre-commit hooks before committing. Default True.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.5.7
    • removedInput schema / properties / auto_start
      Removed value: -{
      -  "default": true,
      -  "description": "For 'phased_push': begin at the lowest phase with unpushed work instead of always 'phase', skipping the inter-phase waits of unchanged upstream phases. Default True; set False to start at 'phase'. Ignored when 'target_project' is set.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / phase
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": 1,
      -  "description": "Starting phase number for 'phased_push'. Default 1."
      -}
    • removedInput schema / properties / target_project
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Optional specific project to push for 'phased_push'."
      -}
  2. First observedv3.5.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, openWorld=false, idempotent=false), lowering the disclosure burden. The description adds a meaningful constraint that this is a typed bulk operation and arbitrary host commands are prohibited, but it does not explain what actually gets committed, how bulk scope is selected, or how pre-commit hooks affect behavior.

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?

The description is two short sentences and front-loads the core action. There is no filler or repetition, making it maximally compact for the information it conveys.

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?

This is an eight-parameter bulk Git mutation tool surrounded by many sibling commit tools, and the description does not explain its relationship to them or clarify the schema's status/cancel/raw parameters. While the output schema and annotations cover return values and safety, the description is too thin to fully orient an agent for this complexity.

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%, so all eight parameters are already documented in the input schema. The description's phrase 'bulk Git operations' loosely aligns with the projects/threads parameters but adds no syntax, format, or selection semantics beyond what the schema provides.

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?

The description states a specific verb and resource ('Commit code') and adds the scope 'typed bulk Git operations,' so the agent knows it commits through a controlled Git surface. It does not distinguish this tool from adjacent commit tools such as rm_git_commit or repository_manager_commit_code_project(s), so it falls 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?

The only usage-like guidance is the constraint that arbitrary host commands are prohibited, which hints that raw command execution belongs elsewhere. It does not say when to choose this tool over rm_git_commit, rm_git_raw, or the repository_manager commit variants, and it gives no exclusions or prerequisites.

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

Deploy Server

Other Tools