Skip to main content
Glama

set_playthrough

Create or edit a game playthrough on one copy, adding new runs or updating type, difficulty, notes, and playtime totals or session-based offsets.

Instructions

Create or edit a playthrough on one copy. create=true adds a new one; otherwise playthrough (id or name) picks the one to edit, and an unsaved default playthrough is saved first. type: firstPlaythrough, replay, speedrun, coop, competitive, continuous, streaming, achievements, challengeRun. playtime_type: session (sum of sessions) or playthrough (set hours/minutes directly). hours/minutes set the manual duration. extra_hours/extra_minutes set playtime_offset: minutes added on top of the session total.

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": "set_playthrough"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
slugYes
typeNo
hoursNo
notesNo
createNo
minutesNo
difficultyNo
extra_hoursNo
playthroughNo
collection_idNo
extra_minutesNo
playtime_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it usefully discloses the side effect that an unsaved default playthrough is saved first, and explains offset accumulation semantics. It does not say whether omitted fields are preserved, whether edits require ownership/permissions, or how failures surface, which matters for a 13-param mutation.

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?

Front-loaded with the core action, then organized parameter-by-parameter in short clauses with no filler. The telegraphic style keeps a 13-parameter explanation compact.

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, but five of thirteen parameters (including difficulty, notes, collection_id, and how a specific copy is targeted beyond slug) are unexplained. For a tool claiming to act on "one copy," the targeting semantics are under-specified.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: it enumerates the accepted type values (firstPlaythrough, replay, speedrun, etc.), contrasts playtime_type session vs. playthrough, and explains hours/minutes as manual duration versus extra_hours/extra_minutes as an offset. Name, slug, notes, difficulty, and collection_id remain undocumented.

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 pair, "Create or edit a playthrough on one copy," and immediately disambiguates the two modes via create=true vs. an existing playthrough. It is distinct from remove_playthrough and set_play_record, though no sibling is named explicitly.

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 clear operational context: create=true adds a new playthrough, otherwise the playthrough parameter selects the one to edit, and an unsaved default is persisted first. It lacks explicit when-not guidance or alternatives such as remove_playthrough or set_play_record.

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