release-notes-mcp

compare_releases

Retrieve all releases between two Git tags, newest first, to identify skipped versions and review changes. Optionally include full release notes.

Instructions

Return every release in repo published after from_tag up to and including to_tag (newest first) — useful when a service jumped several versions.

Bodies are omitted by default (pass include_body=True for the notes text).

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": {
      "repo": "<repo>",
      "from_tag": "<from_tag>",
      "to_tag": "<to_tag>"
    },
    "name": "compare_releases"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes
`to_tag`	Yes
`from_tag`	Yes
`include_body`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Given no annotations, the description does well to disclose key behaviors: newest-first ordering, inclusive to_tag and exclusive from_tag, default omission of bodies, and the include_body flag to override. This covers the main behavioral traits an agent needs to know.

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?

Two sentences, with the main action front-loaded and a single additional note about the include_body parameter. No redundant words, and every clause adds value.

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?

The description is sufficient for an agent to invoke the tool effectively, especially since an output schema exists (so return structure needn't be described). It covers the range semantics, ordering, and body inclusion. Minor missing details like tag existence errors are not critical for selection/invocation.

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?

Schema description coverage is 0%, so the description must explain all parameters. It does: repo identifies the repository, from_tag and to_tag define the range boundaries, and include_body controls whether note bodies are returned. This fully compensates for the missing schema descriptions.

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 tool's function: 'Return every release in `repo` published after `from_tag` up to and including `to_tag` (newest first)'. This specific verb+resource+scope distinguishes it from siblings like list_releases and get_release.

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 provides a clear use case ('useful when a service jumped several versions') and implies the tool is for comparing across a range of releases. It doesn't explicitly name alternatives or exclusion criteria, but the context is sufficient for an agent to select it.

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

Deploy Server