Skip to main content
Glama
Repository Manager

Repository Manager

Validate Status

rm_projects_validate_status

Poll a background validation job by job_id and retrieve results once complete for Python projects.

Instructions

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

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?

The description usefully discloses the background-job model (validate submits, returns job_id immediately; this tool polls), which is real context beyond the annotations. But it never says what happens when job_id is absent, whether results persist after completion, or how the compact summary roll-up differs behaviorally from the full dump. It also sits awkwardly against readOnlyHint=false for what reads as a status query.

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?

Short overall, but the lead sentence duplicates the title and the 'bulk install, build, and validate' line is irrelevant to a status-check tool. The genuinely useful sentence (the job_id polling loop) is buried in the second paragraph rather than front-loaded.

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 present, and annotations carrying the safety profile, the description covers the essential polling loop but omits what a no-job_id call returns and which repositories are in scope. Adequate to invoke, incomplete for confident use.

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 the schema already documents all 11 parameters including job_id and summary. The description adds no parameter-level meaning beyond naming job_id, so the baseline 3 applies.

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 second paragraph does convey the core purpose: poll a validation background job via job_id. But the opening line ('Bulk install, build, and validate Python projects') describes the parent multi-action tool rather than this status tool, and the first sentence only restates the title. An agent has to read past off-topic framing to find what the tool actually does.

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 an explicit workflow instruction ('Use validate_status with that job_id to poll progress and retrieve results once complete'), which routes the agent from rm_projects_validate to this tool. However, there is no guidance on the case where job_id is omitted (job_id is optional, required params = 0), nor any exclusion against siblings like rm_build_status or rm_gates_status.

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