Skip to main content
Glama

Get a game's official updates

get_game_news
Read-only

Official news and patch posts for one game from the last 30 days (newest first): patch notes, events, balance changes, boss/raid content and seasons, each with the official url, source, date, tags and a short LFG Atlas summary (not the publisher's text). Covers every LFG Atlas game with a free official feed (refreshed daily); status no_official_feed means there is no free official feed yet, so never guess. Also returns live context: the game's own player count (with source and scope, never LFG Atlas traffic) and how many LFG Atlas posts are open. Always name the source and link the official post.

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": {
      "game": "<game>"
    },
    "name": "get_game_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOptional: only patch, event, balance, boss or season posts
daysNo
gameYesGame slug or name, e.g. osrs, dragonwilds, cs2
liveNoInclude live player count and open LFG post count (default true)
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnly/openWorld hints, it discloses that feeds are refreshed daily, that summaries are LFG Atlas's own condensation rather than publisher text, and that the player count reflects the game's own population with a stated source and scope — explicitly not LFG Atlas traffic. It also names the no_official_feed status value, which is exactly the kind of failure-mode behavior an agent needs.

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 description is dense and front-loaded, starting with what is returned before the caveats and the citation instruction. It is long and the parenthetical asides accumulate, but nearly every clause carries distinct information.

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?

With no output schema, the description carries the full burden of describing returns and does so: url, source, date, tags, a short summary, plus live player count and open post count, and a named status for missing feeds. Nothing an agent needs to call or interpret the result is missing.

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 60% and the description compensates for most of it: it establishes the 30-day window behind 'days', maps the tag categories (patch, event, balance, boss, season) to the enum, and explains what 'live' actually returns (game's own player count plus open LFG post count). Only 'limit' is left entirely to the schema.

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 opens with a specific verb and resource ('Official news and patch posts for one game'), pins the scope (last 30 days, newest first) and enumerates content types (patch notes, events, balance changes, boss/raid, seasons). It also lists the returned fields, so an agent knows exactly what it fetches without opening the schema.

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

Usage Guidelines4/5

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

It tells the agent when results are unavailable ('status no_official_feed means there is no free official feed yet, so never guess') and how to present output ('Always name the source and link the official post'). It stops short of explicitly routing to a sibling for cross-game or player-count-only queries, so it is strong context but not full when/when-not/alternatives guidance.

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