GAMES.GG

Get releases and events

get_calendar

Read-onlyIdempotent

Use for new and upcoming video game releases, what comes out this week, next week or this month, release dates by platform such as PS5, Xbox, Switch or PC, and gaming events and showcases. from and to are UTC dates (YYYY-MM-DD) or months (YYYY-MM); the default is the current UTC month. type is release or an event type; game is a slug from find_game or a title. Returns releases and gamingEvents. Each release has a gameUrl when available; hubUrl is the GAMES.GG calendar page. An event's url identifies its original source. A localized hubUrl does not mean the data is translated. Free accounts see seven dates including today in UTC. Always pass the user's language in locale; pt maps to pt-BR.

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

Input Schema

Name	Required	Description
`to`	No
`from`	No	UTC date YYYY-MM-DD or inclusive month YYYY-MM. Default current UTC month.
`game`	No	Catalog slug or game title.
`type`	No
`locale`	No	Always pass the user's language as a site locale, e.g. pt or pt-BR, es, fr; default en.

Output Schema

Name	Required	Description
`range`	Yes
`hubUrl`	Yes	GAMES.GG deals or calendar page in the requested locale.
`locale`	Yes
`locked`	No
`releases`	Yes
`gamingEvents`	Yes
`localeFallback`	No
`pinnedReleaseIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

removedOutput schema / properties / upsell

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "ctaUrl": {
-      "format": "uri",
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "reason": {
-      "enum": [
-        "deals_locked",
-        "calendar_beyond_7_days",
-        "games_plus_info"
-      ],
-      "type": "string"
-    },
-    "retry": {
-      "additionalProperties": false,
-      "description": "When the user says they upgraded, call this tool again with these arguments. A new membership applies within 10 seconds without reconnecting.",
-      "properties": {
-        "arguments": {
-          "additionalProperties": {},
-          "propertyNames": {
-            "type": "string"
-          },
-          "type": "object"
-        },
-        "tool": {
-          "enum": [
-            "discover_games",
-            "find_game",
-            "search_guides",
-            "read_guide",
-            "search_editorial",
-            "read_editorial",
-            "get_deals",
-            "get_calendar",
-            "get_games_plus",
-            "preview_membership",
-            "save_game",
-            "unsave_game",
-            "save_guide",
-            "unsave_guide",
-            "follow_codes",
-            "unfollow_codes",
-            "my_games",
-            "my_saved_guides",
-            "my_code_follows"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "tool",
-        "arguments"
-      ],
-      "type": "object"
-    },
-    "trialEligible": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "reason",
-    "message",
-    "ctaUrl",
-    "trialEligible"
-  ],
-  "type": "object"
-}

First observedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds substantial behavior beyond them: the return shape (releases and gamingEvents), what gameUrl and hubUrl mean, that an event's url is its original source, that a localized hubUrl does not imply translated data, and a free-account limitation of seven dates including today in UTC. These are exactly the non-obvious operational constraints 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?

Purpose and date semantics are front-loaded, and nearly every clause carries information. The style is dense run-on fragments and the locale instruction is slightly redundant with the schema's locale description, keeping it from a 5.

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?

For a zero-required-parameter, open-world read tool, the definition covers usage triggers, parameter formats and defaults, return contents, link semantics, quota limits, and localization caveats. Even though an output schema exists, the added notes about url/hubUrl interpretation are the kind of nuance an agent needs to answer correctly.

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?

With 60% schema coverage, the description meaningfully fills gaps: it explains that both from and to accept YYYY-MM-DD or YYYY-MM with the current UTC month as default (the schema documents only 'from'), that type selects release or an event type, that game is a slug from find_game or a title, and that locale should always carry the user's language with pt mapping to pt-BR. Enum values themselves are already in the schema, so it stops short of 5.

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 concrete verb and resource family: new/upcoming video game releases, weekly/monthly release windows, platform-specific release dates, and gaming events and showcases. An agent can immediately tell this is the calendar/date-lookup tool rather than a catalog or deals tool, and the mention of find_game for slugs clarifies the boundary with the game-lookup sibling.

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?

Gives clear positive usage contexts ('what comes out this week, next week or this month', release dates by platform, events and showcases) and points to find_game when a slug is needed. It stops short of explicit when-not guidance or naming a competing tool for deals/editorial content, so 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GAMES.GG tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?