Skip to main content
Glama

get_play_journal

Retrieve your recent play sessions across all games, newest first, to review your gaming journal with pagination.

Instructions

Your recent play sessions across all games (the IB journal), newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_play_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the ordering guarantee ('newest first') and the cross-game scope, which is genuinely useful. It is silent on pagination behavior for limit/offset, on how far back the journal reaches, and on whether the result is filtered to the calling user only.

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?

A single sentence with zero filler, front-loading the resource and its defining traits. It is arguably under-specified rather than overly terse, but nothing in it 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?

An output schema exists, so return values need not be explained, and the tool is simple (2 optional params). Still, for a journal-read tool sitting among many play-record siblings, the definition leaves the pagination contract and the distinction from adjacent listing tools unexplained.

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 the two parameters, so the description must compensate and it does not: neither 'limit' nor 'offset' is mentioned, and the defaults (20/0) are only visible in the schema. The 'newest first' note weakly implies offset paging but adds no real syntax or constraint meaning.

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+resource ('get_play_journal' → 'Your recent play sessions ... the IB journal') and adds scope ('across all games') plus ordering ('newest first'). It does not, however, distinguish it from the sibling read tools such as list_play_records or get_game_stats, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the phrase 'your recent play sessions across all games' suggests a personal, cross-game read, in contrast to per-game tools. There is no explicit when-to-use statement, no prerequisites, and no named alternative to route to when a game-scoped or filtered view is needed.

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