Skip to main content
Glama

Select compatible stable versions

bpj_release_semver_range
Read-onlyIdempotent

Filter and rank stable versions using one exact, caret or tilde x.y.z constraint.

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": {
      "range": "<range>",
      "versions": "<versions>"
    },
    "name": "bpj_release_semver_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
versionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile needs no restatement. The description adds genuinely new behavior: only stable versions are considered and results are ranked, and only three constraint operator styles are supported. It omits the ranking order (ascending/descending) and what happens when nothing matches.

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 no filler, and the constraint forms are stated inline rather than buried. It is tightly compressed to the point that the `versions` input format is lost, so slightly more text would have been justified.

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?

With only two flat parameters and no output schema, the definition is close to sufficient, but it leaves two things an agent needs: how to encode multiple candidate versions in one string, and whether the result is an ordered list or a single best match. Annotations cover the safety side, so the remaining gap is input/output shape.

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% and both parameters carry only titles, so the description must carry the load. It usefully constrains `range` to exact/caret/tilde x.y.z forms, but leaves the critical format of `versions` unexplained — a single string of up to 6000 characters with no stated separator or encoding for the candidate list.

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?

"Filter and rank stable versions" states a specific verb pair and resource, and names the three accepted constraint forms (exact, caret, tilde). It is distinguishable from bpj_compare_semver and bpj_release_semver_bump by the filtering/ranking framing, though it never explicitly contrasts with those siblings.

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: the word "stable" hints that prerelease versions are out of scope, and "filter and rank" suggests selecting a compatible subset. There is no explicit statement of when to choose this over bpj_compare_semver or bpj_release_semver_bump, and no stated exclusions.

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.