Skip to main content
Glama

Read the game’s publications

get_publications
Read-onlyIdempotent

The game’s latest publication on each destination, newest first. A destination with no publication on record is absent, which does not mean never published: what each destination serves is get_application activeArchives. platform is PLAYGAMA_SANDBOX — the sandbox, published by publish_sandbox — or PLAYGAMA — the catalog, published by send_playgama_catalog_update or from the console. Each has id, releaseId, archive (null only once that archive is gone), startedAt, updatedAt and status — IN_PROGRESS while its archive is built and published, PUBLISHED once its build went live, FAILED when it never did, with no reason given — and retryAfterSeconds, the wait before reading again while IN_PROGRESS, null otherwise. After a publish, read it again at that pace until it leaves IN_PROGRESS; on FAILED tell the developer, a new publish starts over. What the sandbox serves now is always get_sandbox_state site.revision. A publish with no answer may still land after any read, so never tell the developer it did not: compare with the publication read before the call — a new releaseId naming this archive is a publication of this archive, that call’s or another’s: follow it; otherwise the outcome is unknown: say so — another publish is a new request, on a new yes.

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": {
      "applicationId": "<applicationId>"
    },
    "name": "get_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYesGame id from list_applications

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / applicationId / description
      Previous value: -"Application (game) id, as returned by list_applications"New value: +"Game id from list_applications"
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: absence means 'no publication on record' and not 'never published,' the full `status` lifecycle (IN_PROGRESS/PUBLISHED/FAILED with no reason given), `retryAfterSeconds` being non-null only while in progress, and the race where a publish with no answer may still land after any read. The comparison-by-`releaseId` rule and 'say the outcome is unknown' instruction are exactly the non-obvious behaviors 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.

Conciseness3/5

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

The critical scoping statement is front-loaded and the content is all relevant, but the prose is dense and the closing passage — 'another publish is a new request, on a new yes' — is opaque enough to be misread. Several sentences pack three or four clauses (status meanings, retry cadence) where a short list would read faster. Length is defensible given no output schema; the phrasing is not.

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?

With no output schema, the description takes on the return shape and does so thoroughly: `id`, `releaseId`, `archive`, `startedAt`, `updatedAt`, `status`, `retryAfterSeconds`, plus what null `archive` means. The platform enumeration and its publishing siblings are also covered. The only shortfall is that the race-condition paragraph is ambiguous about the exact comparison procedure, leaving the agent to interpret 'a new `releaseId` naming this archive.'

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 coverage is 100% and the single `applicationId` parameter is already documented as 'Game id from list_applications.' The description refers to 'the game' and 'each destination' but adds no format, sourcing, or edge-case detail about the id itself. Baseline 3 applies when the schema carries the parameter semantics.

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 opening sentence states a specific resource and scope: 'The game’s latest publication on each destination, newest first,' i.e. a per-platform latest-publication read. It then explicitly separates itself from siblings by saying what each destination serves is get_application `activeArchives` and what the sandbox serves now is get_sandbox_state `site.revision`. An agent can distinguish this from all other read tools in the sibling list without opening a 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 gives concrete usage conditions: read this after a publish, poll at `retryAfterSeconds` while IN_PROGRESS until it leaves that state, and on FAILED tell the developer that a new publish starts over. It also redirects to get_application and get_sandbox_state for the alternatives. It never states an explicit negative case (e.g. 'do not use this to check what is live right now'), but the routing context is clear.

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