Skip to main content
Glama
Repository Manager

Repository Manager

Raw

rm_git_raw

Execute typed bulk Git operations across repositories—clone, pull, push, add, commit, or raw Git commands—while blocking arbitrary host commands and tracking background jobs.

Instructions

Raw (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_raw"
  }
}

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.4/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds a meaningful safety constraint by stating arbitrary host commands are prohibited, but it does not disclose side effects, permission requirements, or what 'bulk' operations affect across repositories.

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 'Raw (rm_git)' is redundant with the name and title. The second sentence is useful but the overall brevity leaves the tool under-specified for an eight-parameter operation.

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?

For an eight-parameter tool with action-like behavior and many sibling alternatives, the description omits the actions, the meaning of command and job_id, and any workflow context. The output schema covers return values, but the description is not complete enough to guide correct invocation.

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 schema. The description adds no parameter-level meaning beyond the word 'bulk' and does not explain the command, job_id, or action-related fields; baseline 3 is appropriate when the schema carries this burden.

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

Purpose2/5

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

The description mostly restates the name and title with 'Raw (rm_git)' and offers only the vague phrase 'Typed bulk Git operations.' It never states that the tool executes a specified Git command, which the schema reveals, and it does not distinguish itself from the many specific sibling tools like rm_git_status or rm_git_commit.

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 guidance on when to use this tool instead of the numerous specific Git siblings, nor any explanation of the action-based routing implied by the schema. The only usage-related content is the prohibition on arbitrary host commands, which is a constraint rather than selection guidance.

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