Skip to main content
Glama

Play history

mister_play_history
Read-only

Inspect recently played or most played games across MiSTer devices, with one row per game and launchable refs to relaunch titles immediately.

Instructions

<use_case> Inspect recently played or most played games across MiSTer devices. </use_case> <important_notes>

  • Aggregated from Zaparoo Core logs on hardware.

  • Each row includes a launchable ref to immediately relaunch a game. </important_notes>

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

Input Schema

NameRequiredDescriptionDefault
hostNoMiSTer name from mister_get_status. Omit when the call already says which (a ref does).
modeNorecent: last played first, one row per game. top: most played by total time.recent
limitNo
systemNoA system id from mister_list_systems, e.g. 'SNES' or 'Genesis'.

Output Schema

NameRequiredDescriptionDefault
entriesYes
unavailableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds meaningful context beyond them: the data is aggregated from Zaparoo Core logs on hardware, and each row carries a launchable ref usable for relaunch. That provenance and row-shape information is genuinely useful for deciding whether the data is authoritative.

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?

Two short tagged blocks, use case front-loaded, zero filler. Every line contributes either purpose or non-obvious behavior.

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?

An output schema exists, so return values need not be explained, and the description still usefully mentions the launchable ref in each row. With four optional parameters and a read-only profile, what remains missing is only routing guidance against siblings and the meaning of limit.

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 coverage is 75%: host, mode, and system are documented in the schema itself, while limit is not described anywhere. The description adds nothing about parameter values except indirectly via the 'ref' note that explains why host can be omitted; a baseline 3 is appropriate.

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 resource and scope: inspecting recently played or most played games across MiSTer devices, which names the two result modes directly. It is clearly distinct from siblings like mister_search_games and mister_launch, though it never explicitly contrasts itself with them.

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?

The <use_case> block implies the situation (wanting to see play history), and the schema's mode enum clarifies recent vs top. However, there is no explicit when-to-use versus alternatives such as mister_search_games, nor any statement of exclusions or prerequisites.

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