Skip to main content
Glama

Distribute Software

AI lab releases

get_releases
Read-onlyIdempotent

Model and product releases posted by the AI labs themselves (newsrooms, changelogs and model lists), newest first.

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": {
      "context": "<context>"
    },
    "name": "get_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
labNoOnly this lab: an id from list_labs, e.g. 'openai' or 'anthropic'.
limitNoMost releases to return. Default 20.
sinceNoOnly releases on or after this day, YYYY-MM-DD.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
include_updatesNoAlso return product updates, not only releases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is covered without the description. The description adds useful context beyond that: the sources are first-party lab channels and results are ordered newest-first. It does not disclose pagination behavior or whether results are capped, which leaves a gap for a list tool.

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 compact sentence that front-loads the resource and appends the qualifying detail (source types) and ordering. No wasted wording, though it does not separate description from scope or usage guidance.

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 7 parameters, one required, and no output schema, the definition is not fully self-sufficient: the description never explains pagination, result volume, or how to narrow to a single lab, leaving the agent to rely entirely on the schema. Since coverage is 100 percent, the gap is modest but real for a list tool with an analytics-heavy parameter set.

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?

No credit needed since schema description coverage is 100%; each parameter including lab, since, limit, include_updates and the analytics fields is fully documented in the schema. The description adds a little framing by implying the default view is releases-only and recency-ordered, which explains how the result set behaves around include_updates and since. Baseline 3-4 is appropriate given the schema carries the load.

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 resource (model and product releases), its provenance (posted by AI labs themselves via newsrooms, changelogs, model lists) and the ordering (newest first). An agent knows exactly what data comes back. It stops short of naming a sibling it differs from, so it is clear but not sibling-differentiated.

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 emphasis on first-party lab sources suggests this is for official announcements rather than general news stories, and 'newest first' hints at recency-driven queries. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as search_stories or get_story, and list_labs is only mentioned in the schema, not here.

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