Skip to main content
Glama

list_playthroughs

Retrieve playthroughs and their sessions for a specific game copy, including dates, minutes, status, and notes.

Instructions

List playthroughs of one copy with their sessions (date, minutes, status, notes). A copy always shows a default "Playthrough" until you save one.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one genuinely non-obvious behavior: a copy always shows a default "Playthrough" entry until one is saved, which prevents the agent from misreading results. It does not state that the operation is read-only, nor anything about permissions, pagination, or ordering of the sessions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the scope front-loaded and no filler; the second sentence about the default playthrough is the kind of detail that earns its place.

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?

The output schema exists, so return values need not be described, and the default-playthrough caveat covers result interpretation well. However, for a two-parameter tool with zero schema descriptions, the definition leaves the caller guessing about slug and collection_id, which is the main 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% for both parameters, so the description must compensate and largely does not. "of one copy" loosely hints that slug identifies the copy, but it never defines slug, and collection_id is completely undocumented in both schema and description.

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 ("List playthroughs of one copy") and even names the returned session fields (date, minutes, status, notes), so the agent knows what it gets back. It does not differentiate itself from nearby siblings such as list_play_records or get_play_journal, which is the only thing keeping it from a 5.

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; the agent must infer from "of one copy" that this is the per-copy playthrough view. No alternative tool is named, so choosing between this and list_play_records/get_play_journal is left entirely to inference.

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