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

mcp-repo-release-tools

Will this commit subject pass the repo's hooks?

rrt_validate_commit
Read-onlyIdempotent

Validate a commit subject against Conventional Commits before committing, optionally applying branch-specific commit type restrictions, to catch invalid messages early.

Instructions

Check a commit subject against Conventional Commits as this repo enforces it, before you commit.

Prefer this over rrt-hooks commit-msg in a shell: the subject is passed as a string argument, so backticks, quotes, !, and $ in the message cannot be mangled by shell quoting. Honors [[tool.rrt.commit_types]] and extra_commit_types from config, as the hook does. Pass branch (the branch the commit lands on) to also apply that branch type's commit_types restriction; without it the restriction is not checked.

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": {
      "subject": "<subject>"
    },
    "name": "rrt_validate_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNo
subjectYes

Output Schema

NameRequiredDescriptionDefault
validYes
reasonNo
subjectYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint), and the description adds real behavioral context beyond them: it honors [[tool.rrt.commit_types]] and extra_commit_types from config exactly as the hook does, and it discloses the conditional branch-type restriction. A caller knows the result depends on repo config, not just the literal input.

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 core action and the pre-commit timing are front-loaded, followed by the shell alternative and then the branch caveat. Every sentence contributes a distinct decision-relevant fact with no repetition.

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 two-parameter validation tool with an output schema available, the description covers the config dependency, the optional branch restriction, and the recommended invocation path. Nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the burden, and it does explain `branch` well: it is the branch the commit lands on, it activates that branch type's commit_types restriction, and omitting it skips that check. `subject` gets less explicit treatment (only that it is a string argument immune to shell mangling), which leaves a small gap given zero schema documentation.

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?

States a specific verb and resource ('Check a commit subject against Conventional Commits'), names the constraint source ('as this repo enforces it'), and gives the timing ('before you commit'). This cleanly separates it from rrt_validate_branch, the nearest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent away from the shell alternative ('Prefer this over `rrt-hooks commit-msg` in a shell') and gives the reason (shell quoting mangling). It also states a conditional usage rule for the optional branch parameter, including what is NOT checked when it is omitted.

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