Skip to main content
Glama

list_play_records

Lists every Play Record category (key/value, checklist, progress, table, text) and its numbered rows for one game copy, read-only, so you can review saved gameplay data.

Instructions

Read the Play Records of one copy: every category (key/value, checklist, progress, table, text) and its rows, numbered from 1. 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_play_records"
  }
}

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
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does usefully declare "Read-only" and disclose the return structure (all categories with numbered rows), but it says nothing about permissions/authentication needed, whether collection_id narrows results, or what wait_ms actually does (block until data is ready?), which matters for a tool with a wait parameter.

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?

A single tight sentence with the core action front-loaded, followed by the scope of returned data and the read-only flag. No filler; only the unexplained parameters represent wasted opportunity rather than wasted words.

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 return values need not be described in detail, and the description covers what is returned at a high level. However, with no annotations and zero schema coverage on two of three parameters, the definition is not complete enough for reliable invocation.

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%, so the schema gives no meaning for slug, wait_ms, or collection_id. The description only indirectly explains slug ("one copy") and leaves wait_ms and collection_id completely undefined in both schema and prose, so it does not compensate for the coverage gap.

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?

States a specific verb and resource (read the Play Records of one copy) and adds scope detail by enumerating the category types returned (key/value, checklist, progress, table, text) and the 1-based row numbering. It does not name or distinguish itself from the sibling copy_play_records, which likely reads similar data, so an agent still has to guess between them.

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

Usage Guidelines3/5

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

The phrase "of one copy" hints that the required slug identifies a single copy and that this is a per-copy read, which is implied usage guidance. There is no explicit statement of when to use this versus copy_play_records or get_play_journal, and no prerequisites or exclusions are given.

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