Skip to main content
Glama
Repository Manager

Repository Manager

Build

rm_projects_build

Bulk install, build, and validate Python projects across repositories, with background validation jobs and status polling by job ID.

Instructions

Build (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_build"
  }
}

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds value the annotations cannot: the async background-job contract for validation (immediate job_id, poll via validate_status). It does not disclose the side effects of commit_code staging/committing across all targeted repos, which is the riskiest behavior here.

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, front-loaded with the purpose before the async detail. No filler. It could be tightened further by folding the polling note into a single clause, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, an output schema, and full annotation coverage, the description only needs to cover the non-obvious runtime contract, which it partly does via the job_id flow. But the unexplained 'action' selector and the total absence of sibling differentiation leave an agent unsure how to invoke install vs validate vs the dedicated 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% and the per-parameter descriptions are rich (summary, failed_only, commit_code), so the schema carries the burden. The description adds only the job_id/validate_status linkage. Worse, it repeatedly refers to an 'action' (install/validate/validate_status) that does not exist as a parameter in the schema, which muddies rather than clarifies parameter semantics.

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

Purpose4/5

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

States a specific verb and resource with scope: 'Bulk install, build, and validate Python projects.' The 'bulk' qualifier hints at the multi-repo nature. However, it never distinguishes itself from near-identical siblings like rm_projects_install, rm_projects_validate, rm_projects_validate_status, or repository_manager_build_projects, so an agent cannot tell from this text alone which one to pick.

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?

It gives one genuinely useful workflow rule: 'validate' returns a job_id immediately and you must poll with 'validate_status'. That is real when-to guidance. But there is no guidance on when to use this consolidated tool instead of the dedicated rm_projects_install / rm_projects_validate / rm_projects_validate_status siblings, nor on how the install/build/validate modes are selected.

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