Skip to main content
Glama

Build a monthly CalVer

bpj_release_calendar_version
Read-onlyIdempotent

Build a YYYY.MM.sequence release version from a calendar month and monthly release counter.

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": {
      "year": "<year>",
      "month": "<month>",
      "sequence": "<sequence>"
    },
    "name": "bpj_release_calendar_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes
sequenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and non-open-world behavior, so the description only needs to add context. It adds the deterministic output format but does not describe validation failures or edge-case behavior, which is acceptable for a simple pure function.

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 a single front-loaded sentence with no unnecessary wording. Every phrase contributes to identifying the output format and the input source.

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 simple pure formatter with complete annotations and a constrained input schema, the definition supplies the key return format and input meaning. It could be slightly more complete by explicitly noting sequence formatting or edge cases, but no major invocation detail is missing.

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%, so the description must carry parameter meaning. It maps year/month to "YYYY.MM" and sequence to a "monthly release counter," but it does not spell out all formatting or constraint details, leaving the schema to cover bounds through min/max.

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 and resource ("Build a ... release version") and gives the exact output format "YYYY.MM.sequence". Together with the title "CalVer," this clearly distinguishes it from semver-based release tools.

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?

It implies use for monthly calendar versioning but does not state when to use this tool versus alternatives such as semver tools, nor does it give when-not-to-use guidance. The agent must infer placement from the tool name and format.

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.