Skip to main content
Glama

Latest official game updates

latest_updates
Read-only

Newest official updates across all covered games (default last 7 days, max 30), optionally only one tag (patch, event, balance, boss, season) or one game. Each item has game, title, date, official url, source, tags and a short LFG Atlas summary. Also lists games with no official feed yet.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
daysNo
gameNoOptional game slug or name
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description need not restate safety. It adds useful behavior beyond annotations: the default 7-day window, 30-day maximum, optional single-tag or single-game scoping, item fields, and the fact that games without official feeds are also listed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences, front-loads the core resource, and then adds filtering and return-shape details without filler. Every sentence contributes useful selection or invocation context.

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 read-only listing tool with no output schema, the description supplies the essentials: default and maximum time range, filterable dimensions, returned item fields, and the no-feed caveat. The main omission is limit behavior, but the schema carries its constraints.

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 low at 25%, so the description carries more weight. It explains tag values, day-range defaults and maximums, and game filtering, but it does not explain the limit parameter's purpose or default behavior beyond what the schema already declares.

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 gives a specific verb and resource: 'Newest official updates across all covered games,' with scope details and filter dimensions. It is clear what the tool returns, but it does not explicitly differentiate itself from similarly named siblings such as get_game_news.

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 explains the default time window, maximum range, and optional tag or game filtering, which implies when the tool is useful. However, it does not explicitly say when to use this instead of get_game_news or other update/news-oriented siblings.

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