Skip to main content
Glama
mcp-repo-release-tools

mcp-repo-release-tools

Preview or apply a release version bump

rrt_bump
Destructive

Preview or apply a version bump across version targets, pins, changelog, lockfiles, generated assets, and release branch/commit, so releases avoid inconsistent hand-edited version strings.

Instructions

Preview or apply a version bump — use instead of editing version strings by hand.

This is the same pipeline as rrt bump (version targets, pins, changelog promotion, lockfile and generated-asset refresh, release branch + commit), so a partial hand-edit will diverge. dry_run=True previews everything and writes nothing. Each result's changed_paths lists every file the bump touched (or would touch under dry_run), relative to the repo root.

level: major | minor | patch | alpha | beta | rc. dry_run=True by default. group: restrict the bump to one [tool.rrt] version group; omit to bump every configured group (one :class:BumpGroupResult per group either way). base: patch | minor | major | auto — the core an alpha/beta/rc bump targets when the current version is FINAL. Same as the CLI's rrt bump rc --base. Omit it to use the group's prerelease_base config, which defaults to the next patch (1.0.0 -> 1.0.1-rc.1; minor -> 1.1.0-rc.1; major -> 2.0.0-rc.1). auto reads Conventional Commits since the last final tag: breaking -> major, feat -> minor, else patch. Ignored once the version is already a pre-release, so rc.1 -> rc.2 never moves the core. scheme: semver | pep440 | calver — the grammar the version is read, bumped and written in. Same as the CLI's rrt bump --scheme. Omit it to use the group's version_scheme config; unset there, it is inferred from the primary target (calendar-shaped -> calver, pep621/python_version -> pep440, else semver).

Runs the SAME pipeline as the rrt bump CLI command (preflight, version targets, pin targets, changelog promotion/generation, lockfile and generated-asset refresh, then release-branch checkout + commit) via :mod:repo_release_tools.commands.bump's shared stage functions, so an MCP bump and a CLI bump of the same repo produce identical results (fixes defect D9: the previous MCP bump only rewrote version-target files and skipped pins, changelog, lockfiles, generated assets, and git branch/commit entirely).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "level": "<level>"
    },
    "name": "rrt_bump"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
groupNo
levelYes
schemeNo
dry_runNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.19.0
    • addedInput schema / properties / base
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / scheme
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  2. First observedv1.18.0

TDQS

A4.4/5.0
Behavior5/5

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

With only destructiveHint=true supplied as an annotation, the description carries the behavioral load well: it enumerates every stage the pipeline performs, states that dry_run=True writes nothing, and discloses that a real run creates a release branch, commits, refreshes lockfiles and generated assets, and promotes the changelog. It also points at the changed_paths output to verify what was touched, which is exactly the side-effect detail the annotation alone lacks.

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?

Front-loaded and reasonably organized with labeled parameter notes, but the CLI-parity claim is made twice and the pipeline stages are listed twice (once parenthetically at the top, once at the bottom). The trailing 'fixes defect D9: ...' changelog is internal history that costs tokens without helping an agent decide or invoke.

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

Completeness5/5

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

For a 5-parameter, destructive, pipeline-level tool with an output schema, every input is defined, side effects and defaults are stated, and the return contract is referenced via changed_paths so return values need no further explanation. Nothing an agent needs in order to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is 0%, so this description has to do all the work and does: level lists the legal values, base defines patch|minor|major|auto plus the concrete config fallback and the 1.0.0 -> 1.0.1-rc.1 example, group explains the one-group-vs-all behavior, scheme lists semver|pep440|calver with the inference rule, and dry_run states its default. This meaningfully exceeds anything the bare schema provides.

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 ('Preview or apply a version bump') and immediately scopes it: version targets, pins, changelog promotion, lockfile and generated-asset refresh, release branch + commit. It positions itself against hand-editing version strings rather than against named sibling MCP tools (rrt_version, rrt_changelog), so differentiation from siblings is implied by scope rather than explicit.

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?

Gives a clear directive ('use instead of editing version strings by hand') and explains the dry_run preview/write distinction with its default. The interaction rules between level, base, and scheme (base ignored once already a pre-release, omit-to-fall-back-to-config) are spelled out. It does not say when to prefer a sibling like rrt_version or rrt_release_check instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.