Skip to main content
Glama

add_play_session

Log a play session on a specific playthrough or copy with date, duration, status, and notes, or pass a session ID to edit an existing entry.

Instructions

Log a play session (date YYYY-MM-DD, hours/minutes played, status, notes) on a playthrough of one copy. Pass session_id to edit an existing session instead. status: start, playing, campaignCompleted (beaten), completed, shelved, dropped. Sessions are capped at 24h each.

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>",
      "date": "<date>"
    },
    "name": "add_play_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
slugYes
hoursNo
notesNo
statusNoplaying
minutesNo
session_idNo
playthroughNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add useful behavior: the 24h per-session cap, the exact status vocabulary with 'campaignCompleted (beaten)' disambiguation, and the session_id edit path. However it says nothing about permissions/auth, what happens when the 24h cap is exceeded, or side effects such as whether a playthrough is auto-created when one isn't supplied.

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?

Front-loaded with purpose, then mode-switching, then value vocabulary, then the constraint. Four sentences, each carrying information. The crammed inline status list is slightly hard to scan but no sentence is wasted.

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?

For a 9-parameter mutation tool with no annotations, the definition covers the semantically risky fields but omits what 'slug' identifies, what collection_id does, and how playthrough relates to session_id. An output schema exists, so return values need not be described. Adequate but with clear gaps for a tool of this complexity.

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 the highest-risk fields: the date format (YYYY-MM-DD), the meaning of hours/minutes/notes, the status value set (which the schema does not enumerate), and session_id as an update switch. The required 'slug' and 'collection_id' are left completely unexplained, which prevents 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?

Opens with a specific verb+resource ('Log a play session') and scopes it to 'a playthrough of one copy', which is more precise than the tool name alone. It also disambiguates the create-vs-edit mode via session_id. It does not distinguish itself from ambiguous siblings like set_play_record, so it stops short of 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 Guidelines4/5

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

Explicitly states the create/update branch: 'Pass session_id to edit an existing session instead.' That is a real when-to-use rule an agent can act on. It offers no guidance on choosing between this and sibling record-mutation tools, so no exclusion guidance.

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