Skip to main content
Glama

set_game_progress

Set or clear a game copy's progress: status, completion, progress bar, notes, playtime, finished playthroughs, and completion date.

Instructions

Set progress on one copy: status (unplayed/playing/played/noStatus), completion (notStarted/unfinished/beaten/completed/continuous/dropped), progress bar 0-100, notes, playtime (hours + minutes, saved as manual unless playtime_type says otherwise), finished playthroughs count, and completion date (YYYY, YYYY-MM or YYYY-MM-DD). playtime_type: manual, playthrough or synced. clear_fields empties: notes, progress, playtime, times_completed, completion_date.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
hoursNo
notesNo
statusNo
minutesNo
progressNo
completionNo
clear_fieldsNo
collection_idNo
playtime_typeNo
completion_dateNo
times_completedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • addedInput schema / properties / completion_date
      Added value: +{
      +  "default": "",
      +  "title": "Completion Date",
      +  "type": "string"
      +}
    • addedInput schema / properties / hours
      Added value: +{
      +  "default": "",
      +  "title": "Hours",
      +  "type": "string"
      +}
    • addedInput schema / properties / minutes
      Added value: +{
      +  "default": "",
      +  "title": "Minutes",
      +  "type": "string"
      +}
    • addedInput schema / properties / playtime_type
      Added value: +{
      +  "default": "",
      +  "title": "Playtime Type",
      +  "type": "string"
      +}
    • addedInput schema / properties / times_completed
      Added value: +{
      +  "default": "",
      +  "title": "Times Completed",
      +  "type": "string"
      +}
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 3000,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
  2. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that playtime is saved as manual unless playtime_type says otherwise and that clear_fields empties specific fields, but it does not explain partial-update behavior, permissions, or what happens to unspecified fields.

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?

The description is dense but front-loaded, starting with the core operation before listing field semantics. It avoids filler, though the long first sentence is somewhat run-on.

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

Completeness4/5

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

For a 12-parameter mutation tool with no annotations, the description covers most field semantics and important side effects such as clear_fields. It is not fully complete because it omits collection_id, slug semantics, and whether unspecified fields are preserved, but the output schema reduces the need to describe return values.

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 description coverage is 0%, so the description must compensate, and it does for most parameters: status and completion enums, progress range, playtime units/default, playtime_type enum, completion_date formats, times_completed, and clear_fields effects. It leaves slug and collection_id unexplained, which keeps it from a 5.

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 states a specific verb and resource: setting progress on one copy, and enumerates the fields it controls. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as set_play_record or set_playthrough.

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?

The description implies usage by naming the operation, but gives no explicit when-to-use guidance, prerequisites, or alternatives. With several sibling tools that also modify game/play data, an agent receives no routing help.

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