Skip to main content
Glama
Sign In
@dwsm/changelog-mcp

@dwsm/changelog-mcp

by dwsmorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_entry

Retrieve the full changelog entry for a specified version number. Access version-specific release notes to review changes.

Instructions

Gibt den vollständigen Changelog-Block einer bestimmten Version zurück.

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": {
      "version": "<version>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersionsnummer (z.B. 0.1.0, 1.2.3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.8

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states it returns data, implying a read operation, but lacks detail about error behavior (e.g., version not found), authorization needs, or side effects. The single sentence is insufficient for behavioral transparency.

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, efficient sentence that communicates core functionality without redundancy. It is front-loaded and achieves conciseness, though it could benefit from slight expansion on the return content.

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

Completeness2/5

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

Given the tool has 1 parameter, no output schema, and no annotations, the description lacks detail on the return format, what constitutes a 'changelog block,' and behavior for invalid input. It is minimally complete for a simple read tool but leaves gaps.

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?

Schema coverage is 100% with a clear description of the 'version' parameter. The description adds no additional meaning beyond what the schema already provides, meeting the baseline for a fully covered 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 clearly states 'Returns the complete changelog block of a specific version,' specifying the action, resource, and scope. It effectively distinguishes from siblings like 'get_current_version' or 'search_changelog' by indicating a targeted retrieval of a full block for a given version.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool over alternatives such as 'preview_entry' or 'search_changelog.' There is no mention of prerequisites, limitations, or context that helps the agent decide which tool is appropriate.

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

Deploy Server

Other Tools