release-notes-mcp

gather_release_notes

Combine release notes from multiple GitHub repositories and tags into a single bundle for synthesizing a unified product release.

Instructions

Bundle raw release notes for an explicit list of selections so they can be synthesized into a single product release.

selections is a list of {"repo": "owner/name", "tag": "v1.2.3"}. Fetches all entries concurrently.

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": {
      "selections": "<selections>"
    },
    "name": "gather_release_notes"
  }
}

Input Schema

Name	Required	Description	Default
`selections`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that it fetches all entries concurrently and that notes are 'raw' (not synthesized), which adds useful behavioral context. However, it does not address error handling, partial failures, or potential side effects (e.g., whether it is purely read-only). Given the fetch-like nature, more depth would improve transparency.

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 compact and front-loaded: it states the core purpose in the first sentence, follows with the parameter format, and ends with concurrency behavior. Every sentence earns its place, with no redundancy or filler.

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

Completeness4/5

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

For a tool with one well-described parameter and an existing output schema, the description covers the essential aspects: what it does, how to specify selections, and a key behavioral trait (concurrency). It does not mention potential prerequisites or failure modes, but given the simplicity and output schema, it is adequately complete.

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?

The input schema has no descriptions and uses a loose additionalProperties string, offering no semantic meaning. The description fully compensates by defining the exact structure: a list of {"repo": "owner/name", "tag": "v1.2.3"}. This is essential for correct invocation and goes well beyond the schema.

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 uses a specific verb 'bundle' with a clear resource 'raw release notes' and states the purpose: to synthesize into a single product release. It distinguishes from sibling tools like get_release (single release) and list_releases by handling an explicit list of selections.

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 clearly indicates when to use this tool: when you have an explicit list of repo/tag selections and want to combine their release notes. It does not explicitly name alternatives or state when not to use it, but the context is unambiguous enough for an agent to select it over siblings.

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

Deploy Server