Skip to main content
Glama
Repository Manager

Repository Manager

Status

rm_git_status
Read-onlyIdempotent

Check Git status and background job progress across repositories, returning compact summaries by default or full detail when needed.

Instructions

Status (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_status"
  }
}

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=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely new fact – that host commands are prohibited – but omits what the tool actually returns, how 'summary' defaults behave, or that status is scoped to a background job. It also sits in tension with a parameter set that includes commit messages and pre-commit flags under a readOnly annotation.

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?

It is short and front-loaded, with no filler sentences. But brevity here comes from omission rather than precision – the two fragments carry almost no information an agent could act on.

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?

With eight optional parameters, an action-dispatch pattern, and no output-schema explanation needed, the description should at minimum clarify that this reports status for a background rm_git job and how it differs from a working-tree status check. Neither is present, leaving a substantial gap for a tool whose siblings are numerous and similarly named.

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 one of the eight parameters is documented in the schema itself, which sets the baseline at 3. The description contributes nothing beyond that – it never mentions path, job_id, projects, summary, or threads, and gives no hint about the action-based dispatch the schema implies.

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 restates the name and title ('Status (rm_git)') without saying what is being reported or measured. 'Typed bulk Git operations' is a generic category label that does not distinguish this tool from rm_git_raw, rm_git_enumerate, or the other rm_git siblings. An agent cannot tell from this text whether it returns repository working-tree status, background job status, or bulk-progress status.

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?

'Arbitrary host commands are prohibited' is the only usage-adjacent statement, and it is a security constraint rather than a when-to-use rule. Nothing says when to pick this over rm_git_raw, rm_git_enumerate, or rm_git_cancel, and the schema's own hint that job_id is required for the 'status' action is never echoed or explained.

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