Skip to main content
Glama
Repository Manager

Repository Manager

Push

rm_git_push

Push Git changes to multiple repositories via typed bulk operations, avoiding arbitrary host commands for secure version control.

Instructions

Push (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_push"
  }
}

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

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnly=false, destructive=false, and idempotent=false, so safety basics are covered. The description adds that this is a typed bulk Git operation and that arbitrary host commands are prohibited, but it omits push-specific behavior such as remote interaction, credential requirements, bulk selection semantics, and failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but the first sentence mostly repeats the tool name and title. The second sentence adds useful scope information, yet two sentences are too thin for a tool with eight parameters and several push-related siblings.

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?

Given eight optional parameters, an output schema, and many sibling tools including repository_manager_push_projects and repository_manager_push_project, the description is substantially incomplete. It does not explain the bulk/projects behavior, how push relates to commit/status/cancel parameters in the schema, or when this tool is the right choice.

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 the schema already documents all eight parameters. The description adds no parameter-level meaning, making the baseline score of 3 appropriate even though the projects parameter is central to the tool's bulk behavior.

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

Purpose3/5

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

The description states the tool is a Git push operation and that it performs "typed bulk Git operations," but it never says what is pushed, to where, or at what scope. It is distinguishable from raw arbitrary command execution, but it does not clearly distinguish rm_git_push from siblings such as repository_manager_push_projects or repository_manager_push_project.

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?

There is no explicit guidance on when to use this tool versus alternatives like repository_manager_push_projects, repository_manager_push_project, or rm_git_raw. The only usage-related signal is the prohibition on arbitrary host commands, which implies a boundary but does not route the agent to the correct sibling.

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