Skip to main content
Glama
Repository Manager

Repository Manager

Enumerate

rm_git_enumerate

Run typed bulk Git operations across repositories, including status, commit, push, pull, and background job control, without allowing arbitrary host commands.

Instructions

Enumerate (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_enumerate"
  }
}

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.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the note that arbitrary host commands are prohibited, which is partially in tension with the schema's 'command' parameter for the 'raw' action, and it says nothing about which operations mutate state, what bulk scope means, or what concurrency via 'threads' implies.

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?

Two short sentences with no filler, but the first is redundant with the name and title, and the brevity comes from under-specification rather than disciplined editing. Nothing is front-loaded about the tool's actual behavior.

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 8-parameter multiplexed tool whose schema references actions ('status', 'cancel', 'raw', 'commit', 'commit_code') without any action property, and the description never mentions action modes at all. Even with an output schema present, an agent has no way to know how to select between the tool's modes or when this is preferable to the dedicated rm_git_* siblings.

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 every parameter is documented in the schema itself (path, job_id, command, message, summary, threads, projects, run_precommit). The description contributes no additional parameter meaning, so the baseline of 3 applies.

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?

"Enumerate (rm_git)" largely restates the tool name and title, and "Typed bulk Git operations" describes a family of siblings (rm_git_add, rm_git_commit, rm_git_status, rm_git_raw) rather than what this specific tool does. Nothing states what is being enumerated or what the tool returns, so an agent cannot distinguish it from the dedicated rm_git_* tools.

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 statement of when to use this tool versus rm_git_status, rm_git_raw, rm_git_commit, or the repository_manager_* equivalents. The only directive present is a prohibition ("arbitrary host commands are prohibited"), which is a constraint, not usage 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