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

mcp-repo-release-tools

Create a policy-compliant branch for this task

rrt_branch_new
Destructive

Create a compliant branch name from a branch type and description, optionally check it out, and return a matching Conventional Commit title for the first commit.

Instructions

Derive a compliant branch name from a type + description.

When dry_run=False, checks it out. Use instead of git checkout -b with a hand-written name — it also returns a matching Conventional Commit title to use for the first commit, though nothing enforces that the caller actually uses it.

commit_type: a branch type of this repo — the built-ins feat|fix|chore|docs|refactor| test|ci|perf|style|build plus any [[tool.rrt.branch_types]] / extra_branch_types. dry_run=True by default.

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": {
      "commit_type": "<commit_type>",
      "description": "<description>"
    },
    "name": "rrt_branch_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo
dry_runNo
commit_typeYes
descriptionYes

Output Schema

NameRequiredDescriptionDefault
errorNo
branchYes
createdYes
dry_runYes
suggested_commit_titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.18.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotation only says destructiveHint=true, and the description usefully clarifies that mutation is conditional and opt-in: nothing happens unless dry_run=False, at which point a checkout occurs. That is genuine added value beyond the annotation. However, it says nothing about failure modes (existing branch, dirty tree) or whether returns are side-effect free in dry-run mode, which matters for a tool flagged as destructive.

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?

The lead sentence front-loads the purpose, and the follow-up paragraphs cover behavior and the commit_type semantics without padding. The aside about non-enforcement of the commit title is slightly chatty but earns its place by setting expectations. Minor tightening is possible but nothing is genuinely wasteful.

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?

An output schema exists, so return format need not be described, and the description even flags the returned commit title. Still, for a four-parameter mutation-capable tool with zero schema descriptions, leaving `scope` and `description` undefined and omitting conflict/precondition behavior leaves real gaps an agent would have to guess at.

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 0%, so the description carries the full burden. It adequately explains commit_type, enumerating the built-in branch types plus the config-extensible ones, and restates dry_run's default meaningfully via the checkout behavior. The `scope` and `description` parameters are never explained, so half the inputs remain opaque.

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?

The description names a specific action and artifact: derive a compliant branch name from a type + description, and optionally check it out. It also frames itself against the raw alternative (`git checkout -b` with a hand-written name), so the agent understands the value-add. It stops short of naming the closest sibling (rrt_validate_branch), so it is clear but not fully differentiated from the tool family.

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?

Explicit routing guidance is present: use this instead of `git checkout -b` with a hand-written name. It also states the safe default (dry_run=True) and warns that the returned Conventional Commit title is advisory, not enforced. Missing is guidance on when to prefer this over rrt_validate_branch or how to handle a branch that already exists.

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