Skip to main content
Glama

List versions

list_versions
Read-onlyIdempotent

List the published registry versions with release dates, version DOIs, entry counts and changes (kinds, the summary from CHANGELOG.md, the number of change items and a link to them). The first listed with default true is used when a version is not given.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
scopeNoScope of the registry: what the entries are and are not.
versionsYes
default_versionYes
doi_all_versionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the default-selection semantics and the shape of the 'changes' payload, which is real behavioral context; but much of the field enumeration overlaps with the existing output schema rather than disclosing new traits like pagination or ordering.

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?

Two sentences, front-loaded with the core action; the long parenthetical is dense but every element names a real returned field. Slightly heavy nesting for a zero-argument call, but nothing is filler.

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 no-parameter, read-only, closed-world listing with an output schema already present, the description covers what matters: what is listed and how defaults are resolved. It stops short of describing ordering guarantees, which would be the remaining gap.

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?

The tool takes no parameters, so the baseline is 4. The description instead explains how a version is inferred elsewhere ('default true'), which is useful cross-call semantics even though no argument exists here.

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 verb and resource ('List the published registry versions') and enumerates what each entry carries (release dates, version DOIs, entry counts, changes). An agent can tell this is a version-catalog tool distinct from the sibling mechanism/search tools, though no sibling is named for contrast.

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 rather than stated: the agent is meant to call this to discover available versions and their DOIs. The final sentence adds a genuinely useful rule for resolving an omitted version argument ('the first listed with default true is used'), but there is no explicit when-to-use or when-not-to-use guidance relative to search or get_mechanism.

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.