Skip to main content
Glama

Bump a stable SemVer

bpj_release_semver_bump
Read-onlyIdempotent

Increment a stable major, minor or patch version and reset lower components.

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>",
      "level": "<level>"
    },
    "name": "bpj_release_semver_bump"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavior beyond that by stating that lower components are reset, but it says nothing about what is returned or how invalid/prerelease input is handled.

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?

A single short sentence with the action and the reset rule front-loaded, and no filler. Every clause earns its place.

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 two-parameter pure computation this covers the core action, but with no output schema the description should indicate the return shape (e.g. a version string) and the expected input format or error behavior. Those gaps leave an agent guessing at the edges.

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 description coverage is 0% and the 'level' parameter has no enum, so the description's enumeration of major/minor/patch carries real meaning. However, it adds no detail on version string format, validation, or failure behavior beyond the schema's own title 'Stable version x.y.z'.

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 gives a specific verb ('Increment') and resource ('stable major, minor or patch version') plus the side effect of resetting lower components. It is clearly distinguishable from compare/range siblings, though it does not name them explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are mentioned. The word 'stable' is the only implicit constraint, hinting that prerelease or build-metadata versions may not be accepted, but this is left for the agent to infer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.