Skip to main content
Glama

list_collection_game_options

Retrieves read-only details for one game in your collection, including per-copy data, progress, acquisition, tags, DLC, playthroughs, and your rating and review. Use it to inspect a game's full collection record.

Instructions

Everything about your copies of one game: per-copy details, progress, acquisition, tags, DLC, play records id, playthroughs, your rating and your review. Read-only.

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": {
      "slug": "<slug>"
    },
    "name": "list_collection_game_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
wait_msNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / wait_ms / default
      Previous value: -3000New value: +0
  2. First observedv1.0.1

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does explicitly declare 'Read-only.', which is genuinely useful safety context, but it says nothing about pagination, rate limits, permissions, or what 'options' means semantically. It also never explains the effect of wait_ms or collection_id on behavior.

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?

One compact sentence plus a two-word safety tag — front-loaded and free of filler. The comma-separated field list is slightly run-on and the fragment 'play records id' is awkward, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description is not obliged to explain return values, and its field enumeration usefully previews the shape. However, for a three-parameter tool with zero schema coverage and no annotations, leaving collection_id and wait_ms undefined is a real completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. 'one game' weakly implies slug is a game identifier, but collection_id and especially wait_ms (default 0) are completely opaque and left to guesswork.

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?

The description names the specific resource (copies of one game in a collection) and enumerates the payload: per-copy details, progress, acquisition, tags, DLC, play record ids, playthroughs, rating, review. That is far more concrete than a name restatement. It stops short of distinguishing itself from look-alike siblings such as get_game, get_game_stats, or list_play_records, but an agent can tell the resource is per-copy collection data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative. The phrase 'one game' implies a single-slug scope, but the agent gets no signal about why to choose this aggregating tool over list_collection, get_game, or the individual list_playthroughs / list_play_records siblings.

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