release-mcp

release_bump

Bumps the release version and triggers a build after a fix is applied to a node's release branch.

Instructions

After a fix landed on a node's release branch: cut the next iterated tag and build it.

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": {
      "coordinate": "<coordinate>",
      "node": "<node>"
    },
    "name": "release_bump"
  }
}

Input Schema

Name	Required	Description	Default
`node`	Yes
`coordinate`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full weight. It describes the action as creating a tag and building, which implies mutation, but does not disclose side effects, prerequisites, or reversibility. The description lacks details about what happens to previous tags or builds.

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 description is a single, front-loaded sentence that conveys the essential action. It is concise and efficient, though the extreme brevity sacrifices parameter and behavioral detail.

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?

Given the tool has an output schema and two undocumented required parameters, the description is minimally adequate. It explains the core action but does not cover parameter meanings or return values. Additional context would improve completeness.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation for the two required parameters ('node', 'coordinate'). The description hints at 'node' from 'node's release branch', but does not clarify what values are valid or how 'coordinate' is used.

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 clearly states the action ('cut the next iterated tag and build it'), the resource (tag on release branch), and the condition ('after a fix landed'). It distinguishes this tool from siblings like 'release_plan' or 'release_approve'.

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?

The description provides an explicit usage context ('after a fix landed on a node's release branch'), implying when to use the tool. It does not explicitly exclude alternatives, but the sibling list makes the distinction clear.

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

Deploy Server