Skip to main content
Glama

List game-data updates

list_data_updates
Read-onlyIdempotent

Lists the points and datasheet updates the installed army data recorded, newest first, as the /data-updates pages show them. Each update has its UTC time, url, total change count and omitted (changes past its stored bound). Without faction, each update lists only the factions it reached with their change counts. With faction, it lists that faction's changes in groups: kind (datasheet-points, datasheet-added, datasheet-removed, detachment-points, detachment-added, detachment-removed, enhancement-points, enhancement-added, enhancement-removed), name, points from and to (per models row for datasheets; null where none), and the url of the page describing it now, or null when it no longer exists. Pass older as before for the next page; null means no older updates.

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_data_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNoThe older cursor from a previous page; omit for the newest updates.
factionNoA faction slug from list_factions, such as necrons, to list only the updates that reached that faction.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read; the description goes well beyond them by specifying ordering (newest first), per-update fields (UTC time, url, total change count, omitted), how output shape differs with and without faction, the full set of change kinds, null semantics for missing points/url, and pagination termination.

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?

Purpose and ordering are front-loaded, and nearly every clause carries interpretive value for the response shape. It loses a point for a dense run-on second sentence and the awkward 'Pass older as before for the next page' phrasing, which takes a moment to map onto the `before` parameter.

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?

There is no output schema, so the description carries the full burden of describing returns — and it does: update envelope fields, faction-summary mode, grouped faction mode, all change kinds, and nullable values. Nothing an agent needs to call or interpret this tool 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 100%, so the baseline is 3; the description still adds meaning by clarifying that faction changes the grouping of returned changes rather than just filtering, and that the cursor yields no older updates when null. The analytics parameters (llm_model, conversation_id) get no additional treatment beyond their schema text.

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?

States a specific verb and resource — listing points/datasheet updates recorded by the installed army data — plus scope (newest first, mirroring the /data-updates pages). No sibling tool covers update history, so the resource is unambiguously distinguishable from list_my_* and list_reference.

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?

Explains the two modes of use clearly: omit faction for a per-update faction summary, or supply faction for grouped per-faction change detail, and it explains cursor paging with 'null means no older updates.' There is no explicit when-not-to-use or named alternative, which keeps it below a 5.

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