Skip to main content
Glama

data-api-code

semver_range_evaluate

Parse Semantic Versioning (SemVer 2.0) versions and evaluate whether candidate versions satisfy ^, ~, >=, <=, or comparator ranges.

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": "semver_range_evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
rangeNo^1.2.3
versionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses only the supported range operators and SemVer 2.0 conformance; it says nothing about return shape (single boolean versus per-version results), how invalid or non-SemVer input is handled, or whether prerelease/build metadata is considered.

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 or repetition. It is efficient, though the compression leaves the input semantics underspecified rather than making every word earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a simple pure computation, but with no annotations, no output schema, and zero parameter descriptions, the definition should explain what is returned and how 'text', 'range', and 'versions' interact. Neither is covered, so an agent must guess the output format before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all three parameters are undocumented in the schema. The description mentions 'versions' and range operators but never explains 'text' — whether it is a version string, a range string, or free-form input — leaving the most important parameter's meaning ambiguous.

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?

States a specific two-part operation: parse SemVer 2.0 versions and test whether candidates satisfy ^, ~, >=, <=, or comparator ranges. This is precise enough to distinguish the tool from any unrelated sibling, though the phrase leaves ambiguous which inputs are being parsed versus which are the range.

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 implied by the semver/range vocabulary, so an agent can infer it is the tool for version-satisfaction checks. However, there is no explicit when-to-use, no when-not-to-use, and no guidance on how to choose between supplying a single version via 'text' versus a list via 'versions'.

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.

Resources