Skip to main content
Glama

Compare SemVer versions

bpj_compare_semver
Read-onlyIdempotent

Compare two SemVer 2.0 versions, including prereleases and build metadata.

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": {
      "left": "<left>",
      "right": "<right>"
    },
    "name": "bpj_compare_semver"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that prereleases and build metadata are handled, which is useful behavioral context, but says nothing about the result format (no output schema exists) or the SemVer rule that build metadata is ignored for precedence.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity contributes to the missing return-value and ordering information elsewhere.

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 two-string pure function with full annotations and no nested objects, most of what an agent needs is present: input domain and comparison scope. The remaining gap is the return semantics (e.g., sign convention or ordering outcome), which is unstated and not covered by an output schema.

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 0% — the only parameter metadata is the titles 'Left version' and 'Right version'. The description compensates by establishing the input domain (SemVer 2.0 strings, prereleases, build metadata), but it never explains left-vs-right ordering, which matters for interpreting the comparison result.

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?

Names a specific verb and resource: compare two SemVer 2.0 versions. The resource (SemVer) is distinct from the compare siblings (bpj_compare_json, bpj_compare_line_sets), so an agent can tell them apart, though the description never explicitly differentiates itself.

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

Usage Guidelines3/5

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

Usage is only implied by the semantics of 'compare two SemVer versions' — there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as the JSON comparison sibling. For a single-purpose utility this is adequate but offers no routing guidance.

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.