Skip to main content
Glama
Repository Manager

Repository Manager

Install

rm_projects_install

Installs, builds, and validates Python projects in bulk, with optional background validation jobs and job status polling for progress and results.

Instructions

Install (rm_projects). Bulk install, build, and validate Python projects.

The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete.

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_projects_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
extraNoInstall group (e.g. 'all') for 'install'.all
job_idNoJob ID to check status for 'validate_status' action.
summaryNoFor 'validate'/'validate_status': return a COMPACT roll-up (counts + failed set + running names) instead of the full per-job dump. Keeps responses inline-returnable at thousands of repos. Set False for the full per-job detail.
threadsNoParallel workers.
output_dirNoDirectory to write the validation-reports for 'validate'.
commit_codeNoFor 'validate': after validation passes, concurrently stage (git add -A), run pre-commit, and commit feature code across ALL targeted repos. Use with commit_message.
failed_onlyNoFor 'validate': target ONLY repositories whose most-recent validation failed (the remediation loop). Ignored if 'repositories' is given. Forces re-validation of that set.
repositoriesNoComma-separated list of specific repositories to target.
commit_messageNoCommit message for the commit_code step. Required when commit_code=True.
generate_reportNoGenerate validation report directory for 'validate'. Default True.
force_revalidateNoIf true, bypass validation cache and force re-validation of all projects.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.5.7
    • removedInput schema / properties / auto_bump
      Removed value: -{
      -  "default": false,
      -  "description": "Automatically run phased_bumpversion if validation passes. Begins at the lowest phase that has repository changes (and cascades to every later phase), skipping unchanged upstream phases.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / auto_push
      Removed value: -{
      -  "default": false,
      -  "description": "Automatically run phased_push if validation passes. Begins at the lowest phase with unpushed work, skipping the inter-phase waits of unchanged upstream phases.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / bump_part
      Removed value: -{
      -  "default": "minor",
      -  "description": "The part of the version to bump (e.g. minor, patch, major) if auto_bump is used.",
      -  "type": "string"
      -}
    • changedInput schema / properties / commit_code / description
      Previous value: -"For 'validate': after validation passes and BEFORE the version bump, concurrently stage (git add -A), run pre-commit, and commit feature code across ALL targeted repos. Ensures untracked/new files are committed (not left for the push safety net). The bump then waits on this step. Use with commit_message."New value: +"For 'validate': after validation passes, concurrently stage (git add -A), run pre-commit, and commit feature code across ALL targeted repos. Use with commit_message."
    • removedInput schema / properties / prune_worktrees
      Removed value: -{
      -  "default": false,
      -  "description": "For 'validate' with auto_bump/auto_push: after the release, prune session worktrees already merged into main (and dangling admin pointers). DESTRUCTIVE. Default False — the release still runs the audit and REPORTS the safe_to_prune/do_not_disturb classification under 'worktree_hygiene_job_id' WITHOUT deleting anything. Never touches active/in-flight or orphaned worktrees.",
      -  "type": "boolean"
      -}
  2. First observedv3.5.1

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is already carried by structured data. The description does add genuinely non-derivable behavior: validate is dispatched as a background job returning job_id rather than blocking. It says nothing about the side effects of 'install' (environment/package mutation) or commit_code (git add + pre-commit + commit across ALL targeted repos), which is the riskiest behavior an agent needs warned about.

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

Conciseness4/5

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

Three short sentences, no filler, with the purpose front-loaded and the async caveat second. The 'Install (rm_projects)' opener is redundant with the title, and the unbacked 'action' terminology introduces mild noise, keeping it out of the top band.

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 a complex multi-modal tool: 11 optional parameters, three encapsulated operations, background-job dispatch, git commit side effects, caching with force_revalidate, and failed_only remediation targeting. The description explains only the validate/validate_status half and leaves install and build entirely undocumented. An output schema exists so return values needn't be explained, but the operation-selection model is missing for a tool of 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 every one of the 11 parameters is already documented in the schema, including the commit_code/commit_message dependency and failed_only precedence. The description adds no parameter meaning of its own beyond the job_id flow. It also refers to an 'action' selector that does not exist as a schema property, which muddies rather than clarifies parameter usage.

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 names a concrete resource (Python projects) and three concrete operations (install, build, validate), so the gist is clear. However, it does not distinguish this combined tool from siblings that do each operation alone (rm_projects_validate, rm_projects_build, repository_manager_install_projects), and the 'Install (rm_projects)' preamble merely restates the name. An agent cannot tell from the text alone why it should pick this multi-purpose entry point over the specialized siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is real guidance for the asynchronous workflow: 'validate' returns a job_id and you must poll with 'validate_status' — that sequencing is explicit and useful. There is no guidance at all on when to use this tool versus the dedicated install/validate/build siblings, or when to prefer 'failed_only' remediation runs versus a normal pass. Usage is implied by the action names rather than stated.

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