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

mcp-repo-release-tools

Will this branch name pass the repo's hooks?

rrt_validate_branch
Read-onlyIdempotent

Validate a branch name against the repository's configured branch-type allow-list and extra types before creation to catch invalid names before pre-commit rejection.

Instructions

Check a branch name against this repo's configured type allow-list before you create it.

Cheaper than creating it and having the pre-commit hook reject it. Honors [[tool.rrt.branch_types]] and extra_branch_types from config, which a hardcoded regex would miss.

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": {
      "branch_name": "<branch_name>"
    },
    "name": "rrt_validate_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch_nameYes

Output Schema

NameRequiredDescriptionDefault
validYes
branchYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.18.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is read-only and idempotent, so the description does not need to repeat safety information. It adds useful behavioral context by saying it honors [[tool.rrt.branch_types]] and extra_branch_types from config, which explains why a hardcoded regex is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded, and has no wasted wording. Each sentence adds concrete value: the action, the timing rationale, and the config-aware behavior.

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 simple one-parameter validation tool with an output schema and read-only/idempotent annotations, the description gives enough context to invoke it correctly. Return-value semantics can be left to the output 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?

There is one parameter, branch_name, and schema description coverage is 0%, so the description must carry the semantic burden. It makes clear that the parameter is the branch name being validated against the configured allow-list, but it does not add format or syntax details beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: checking a branch name against the repo's configured type allow-list before branch creation. It clearly distinguishes this preflight validation from actually creating a branch, which is the relevant sibling behavior.

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?

It explicitly says to use this before creating a branch and explains why: it is cheaper than creating the branch and having the pre-commit hook reject it. It does not explicitly name a sibling alternative or exclusion, but the temporal guidance is clear.

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