Skip to main content
Glama

Look up a co-op game

get_coop_game
Read-onlyIdempotent

Look up one game's co-op facts on CoopGamesDB: how many can play online and on one screen, whether it has online, split-screen, same-couch or LAN co-op, platforms, price per copy and for the whole group, its lowest price lately, Steam reviews, who it suits, store links, and where each fact comes from (facts nobody has confirmed yet are marked unverified). Use it for questions like "is It Takes Two split screen?", "how many players can play Lethal Company?", "can you play Valheim online?" or "how much is Helldivers 2 for 4 of us?". Also knows co-op games not out yet: their release date and how many players their developer states. Takes the name as people write it, and suggests the closest names when none matches.

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

Input Schema

NameRequiredDescriptionDefault
gameYesThe game’s name as people write it, such as "It Takes Two"; its CoopGamesDB address name works too.
groupSizeNoHow many will play, to price the copies the whole group needs.

Output Schema

NameRequiredDescriptionDefault
gameYes
foundYes
upcomingYes
suggestionsYes
otherMatchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and non-open-world, so the safety profile is settled. The description adds genuinely new behavior: provenance per fact, unverified marking, upcoming-title handling, and fuzzy name suggestion when no exact match is found. It doesn't discuss rate limits or empty/failed lookup behavior, keeping it at 4.

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 purpose is front-loaded and the example questions are efficient. However, the long middle enumeration of returned fields (platforms, prices, reviews, store links, provenance) overlaps heavily with the existing output schema and makes the description a run-on that could be trimmed.

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 two-parameter single-record lookup with full schema coverage and an output schema, the description covers scope, edge cases (no match, unreleased games, unverified facts), and the kinds of questions it answers. Nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so both parameters are already documented in the schema, including groupSize's purpose. The description only echoes the name-handling behavior and implies pricing for the whole group, adding little beyond structured fields.

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?

Opens with a specific verb and resource ("Look up one game's co-op facts on CoopGamesDB") and then enumerates the returned facts. The emphasis on "one game" implicitly separates it from the multi-game discovery siblings such as find_coop_games and list_new_and_upcoming_coop_games.

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 example questions that map cleanly onto this tool's scope (split-screen, player count, online support, group pricing, unreleased titles), which is strong usage context. It stops short of explicitly naming a sibling or stating when not to use it, so it falls short of 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