Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Semver compare, version check: compare two version numbers and say which is newer

semver
Read-only

Semver compare of two semantic versions (1.2.3, pre-releases like 2.0.0-rc.1 handled by the SemVer rules): which is newer, plus the next major, minor and patch versions of the first. Use to decide whether an upgrade is a major change. Example: a=1.10.0, b=1.9.3. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "semver"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst version
bYesSecond version

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, non-idempotent behavior; the description adds that each call is charged, repeats are not free, failed calls are free, and the first 25 are free. It also clarifies that pre-release versions are handled by SemVer rules and that the tool only computes and changes nothing. There is no contradiction with the annotations.

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?

It is front-loaded with the operation and output, then the use case, example, pricing, and safety profile. The pricing sentence is longer than strictly necessary but contains operationally relevant cost information; overall it is well organized.

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-parameter, no-output-schema utility, the description explains inputs, outputs, SemVer handling, pricing, and side-effect profile. Remaining gaps such as exact response shape or invalid-version error behavior are minor.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds that a and b are semantic versions, accepts pre-release forms like 2.0.0-rc.1, and gives the example a=1.10.0, b=1.9.3. It does not discuss invalid inputs, but meaning is improved beyond the field labels.

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 names a specific operation—comparing two semantic versions—and states it also returns the next major, minor, and patch versions of the first. It is clear about what is compared, though it does not explicitly differentiate from any sibling tool.

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?

It gives a concrete use case: deciding whether an upgrade is a major change, supported by an example. It does not state when not to use it or name alternatives, so guidance is adequate but incomplete.

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.