Skip to main content
Glama
Repository Manager

Repository Manager

Validate

rm_projects_validate

Validate Python projects in bulk by launching a background job, then poll its job_id to track progress and retrieve results.

Instructions

Validate (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_validate"
  }
}

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.9/5.0
Behavior4/5

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

Annotations mark this non-read-only and non-idempotent, and the description adds the key behavioral fact those annotations cannot: the call returns immediately with a job_id rather than results. It omits that commit_code=True performs git staging, pre-commit, and commits across all targeted repos, which is a significant write side effect only documented inside the schema.

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 with the async contract front-loaded after a brief lead-in. The parenthetical '(rm_projects)' and the install/build enumeration are low-value filler that could be trimmed.

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

Completeness4/5

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

Output schema exists, so return values need not be explained, and the rich parameter descriptions cover the many flags. The description supplies the missing piece — the background-job execution model. Its only gap is failing to surface the commit_code write path outside the schema.

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 11 parameters already carry their own docs, including the summary, failed_only, and commit_code semantics. The description adds only the job_id lifecycle concept, which is documented on the parameter anyway. Baseline 3 is appropriate.

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 clear verb+resource ('Validate Python projects') and separates itself from the sibling rm_projects_validate_status by describing the async submit/poll split. The opening line 'Bulk install, build, and validate' muddies the scope, since install/build live on sibling tools and no 'action' parameter exists in the schema to switch modes.

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

Usage Guidelines4/5

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

Explicitly names the follow-up tool and the exact handoff value: 'Use validate_status with that job_id to poll progress and retrieve results once complete.' That is a real when-next-step rule. It stops short of saying when to prefer this over rm_projects_build or repository_manager_validate_single_project.

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