Skip to main content
Glama

Primary Source Commodities

Next Releases With Last Print

releases.next
Read-onlyIdempotent

The release calendar joined to what each report last said: expected_at with a real Eastern offset, the last print's values, week-on-week change, the 5-year comparison, and a surprise label. Use this instead of calendar.get when you need the numbers as well as the timing — calendar.get answers only when. last is null when nothing is stored yet and surprise_label is null when no 5-year band exists; neither is ever guessed. Paid.

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": "releases.next"
  }
}

Input Schema

NameRequiredDescriptionDefault
release_idNoOne release id, as published by calendar.get
window_daysNoKeep only releases expected within this many days. Releases with no known date are excluded by a window.

Output Schema

NameRequiredDescriptionDefault
releasesYesReleases, soonest first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds value beyond that by disclosing null semantics (`last` is null when nothing is stored, surprise_label is null when no 5-year band exists) and a data-integrity guarantee ("neither is ever guessed"), plus the "Paid" cost signal. It stops short of describing pagination or result ordering, which keeps it from a 5.

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?

The content is front-loaded: the payload list comes first, followed by the sibling routing rule, then the null/cost caveats. It is dense but every clause carries information; the only cost is heavy semicolon and em-dash packing that slightly hurts scannability.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description still gives the agent the field-level gist and the null behavior it needs to interpret results. Combined with the paid-cost note and the sibling routing, nothing required to call this correctly is missing.

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 description coverage is 100% and the enum of release ids is fully documented in the schema, so the schema carries the parameter burden. The description adds only an indirect constraint — that releases without a known date are excluded by a window — and does not clarify window_days syntax or units beyond what the schema states. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-plus-resource framing and then enumerates the exact payload: expected_at with a real Eastern offset, the last print's values, week-on-week change, the 5-year comparison, and a surprise label. It explicitly contrasts itself with calendar.get ("answers only *when*"), so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit selection rule — use this instead of calendar.get when you need the numbers as well as the timing — and names the alternative along with the condition that picks the sibling. The only minor gap is that it does not spell out a when-not case, but the contrast with calendar.get effectively supplies one.

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