Skip to main content
Glama
Repository Manager

Repository Manager

Validate and release

repository_manager_validate_and_release

Validates multiple projects in parallel and reports whether all validation checks passed, so you can decide whether to release.

Instructions

Validate projects in parallel and report whether all passed.

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": "repository_manager_validate_and_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.5.7
    • removedInput schema / properties / auto_bump
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
    • removedInput schema / properties / auto_push
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
    • removedInput schema / properties / bump_part
      Removed value: -{
      -  "default": "minor",
      -  "type": "string"
      -}
  2. First observedv3.5.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so safety is partly covered; the description contributes the 'parallel' execution trait. But it omits the tool's defining mutation, 'release' (what gets released, whether it happens only on success, what state changes on failure), which is exactly the beyond-annotation context needed for a non-read-only tool.

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?

One sentence, front-loaded, no filler. Brevity is appropriate but it is underspecified rather than tight — there is room for the same length to carry the release semantics.

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?

An output schema exists so return formatting needn't be explained, but for a tool whose name promises validation plus release, with an undocumented parameter and no explanation of failure behavior or release effects, the description leaves too much for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'threads' has 0% schema description coverage and no default/range explanation anywhere. The phrase 'in parallel' vaguely gestures at concurrency, but the description never connects it to 'threads' or explains the null default — with low coverage the description was supposed to compensate and doesn't.

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 states a concrete verb and scope (validate projects in parallel, report pass/fail), which is more specific than the name alone. However, it says nothing about the 'release' half of the tool name, so an agent cannot tell what releasing entails or how this differs from nearby validators like repository_manager_validate_single_project or rm_projects_validate.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative, despite many sibling validators (validate_single_project, test_projects, rm_projects_validate, rm_projects_validate_status) that an agent must choose between. The parallel aspect hints at bulk usage but never says so explicitly.

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