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

@dwsm/changelog-mcp

by dwsmorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_next_version

Calculates the next version number from a bump type (major, minor, or patch) to automate versioning in changelog management.

Instructions

Berechnet die nächste Versionsnummer basierend auf dem Bump-Typ.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_next_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
bumpNoArt des Version-Bumps (Default: "patch")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.8

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so description carries full burden. It discloses it calculates (a read-only computation) but doesn't state whether it has side effects or requires any preconditions. Adequate for a simple calculation, but could specify it's read-only.

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?

Single sentence is concise and front-loaded. No unnecessary words, but could benefit from brief additional context like 'given a current version'.

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?

For a one-param computation tool with no output schema, the description is minimally adequate. However, it doesn't mention that it relies on a current version (presumably from get_current_version), which could be helpful for context.

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% and already describes bump as an enum with default 'patch'. Description adds 'based on the bump type' which aligns but adds no new info beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates the next version number based on bump type (verb 'berechnet', resource 'Versionsnummer'). It distinguishes from siblings like get_current_version which returns the current version, but the differentiation is implicit.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., when to bump vs. just retrieving version). No explicit context or exclusion statements.

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