Skip to main content
Glama

submit_playtime

Submit time-to-beat and completion playtimes to Infinite Backlog for copies marked Beaten or Completed; confirmation is required, and resubmitting updates data since entries cannot be deleted.

Instructions

Submit your time to beat and time to complete a game to Infinite Backlog's public playtime data. Needs a copy marked Beaten or Completed and confirm=true. There is no delete: a submission can only be changed by submitting again.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo
beaten_hoursNo
beaten_minutesNo
completed_hoursNo
completed_minutesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that this writes to public shared data, that it is irreversible in the sense that there is no delete and changes only via re-submission, and that a qualifying copy plus confirm=true are required. It omits auth/account requirements and any rate or moderation behavior, and doesn't explain how partial time fields are handled.

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?

Three short sentences, each earning its place: purpose first, prerequisites second, irreversibility third. The front-loading of the write target and the explicit 'no delete' warning are exactly what an agent needs up front, with no filler.

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 mutation tool with no annotations, the description covers the preconditions and the reversibility story, and an output schema exists so return values need not be explained. The remaining gap is the beaten/completed distinction and the time-field formats, which leaves an agent able to call it but uncertain about some argument semantics.

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

Parameters3/5

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

Schema description coverage is 0% across six parameters, so the description must compensate, and it only partly does: it explains confirm=true and the pairing of beaten/completed times with copy status. It does not clarify units or accepted formats for the string hours/minutes fields, what the empty-string defaults mean, or how beaten versus completed are distinguished semantically.

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 uses a specific verb and resource ("Submit your time to beat and time to complete a game") and names the target dataset (Infinite Backlog's public playtime data), so the write intent is unmistakable. It does not explicitly contrast itself with siblings like list_playtime_contributions or add_play_session, but the verb 'submit' already separates it from the 'list' family.

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?

It states concrete preconditions for calling: the game must have a copy marked Beaten or Completed, and confirm=true must be supplied. It also explains the update path (re-submit to change) and the absence of a delete path, giving clear when-to-use context. It stops short of naming an alternative tool for cases where those preconditions don't hold.

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