Skip to main content
Glama

New and upcoming co-op games

list_new_and_upcoming_coop_games
Read-onlyIdempotent

List co-op games coming out soon, from Steam's most wishlisted upcoming co-op games with release dates as precise as their developers give them, or co-op games released in the last weeks, optionally only those for the group's size, platforms and way of playing. Use it for "upcoming co-op games", "new co-op games this month", "co-op games coming in 2027" or "what co-op games just came out?". Upcoming games say how many players their developer states; new ones have the same facts as any game. Each game links its CoopGamesDB page.

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

Input Schema

NameRequiredDescriptionDefault
whenNo"upcoming" (the default): not out yet, with release dates; "new": out in the last weeks.
limitNoHow many games to list (6 unless asked).
modesNoHow the group plays together; a game must offer every one listed: "online", "local" (same couch), "split" (split screen), "lan".
playersNoHow many people will play together: only games that fit a group this size.
platformsNoPlatforms the group plays on: games on at least one of them. "pc" covers Steam and Windows.

Output Schema

NameRequiredDescriptionDefault
whenYes
totalYes
listUrlYes
releasedYes
upcomingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
      -  "pc",
      -  "ps5",
      -  "xbox",
      -  "switch",
      -  "mac",
      -  "linux",
      -  "mobile",
      -  "web"
      -]New value: +[
      +  "pc",
      +  "ps5",
      +  "xbox",
      +  "switch",
      +  "mac",
      +  "linux",
      +  "mobile",
      +  "ios",
      +  "android",
      +  "web"
      +]
    • changedInput schema / properties / platforms / maxItems
      Previous value: -8New value: +10
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description still adds real context: the data source (Steam's most wishlisted upcoming titles), the release-date precision caveat, the distinction in what's returned for upcoming vs new games, and the CoopGamesDB page link.

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?

Front-loaded with the core purpose, then usage examples, then return-behavior notes — a logical order with no filler sentences. It is somewhat dense and runs long with four quoted example queries, but every sentence carries information.

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?

An output schema exists, so return shape needn't be explained, and the description covers the parts that matter: defaults (upcoming, 6 results), data provenance, and the precision caveat on release dates. The only remaining gap is the absence of routing guidance relative to sibling discovery tools.

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%, so the baseline is 3; the description only loosely restates the filters ('for the group's size, platforms and way of playing') and confirms the 'upcoming' default. It adds no detail beyond the schema's match semantics (any-platform vs all-modes) and no guidance on sensible filter combinations.

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?

Specific verb and resource: 'List co-op games coming out soon' with an explicit split between 'upcoming' and 'released in the last weeks'. It does not name or contrast with the sibling find_coop_games, so an agent must infer that this is the date-scoped variant, but the resource and scope are unambiguous.

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 concrete trigger phrasings ('upcoming co-op games', 'new co-op games this month', 'co-op games coming in 2027', 'what co-op games just came out?') that map cleanly onto the when enum. It stops short of stating when to prefer a sibling like find_coop_games, so no exclusions are provided.

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