Skip to main content
Glama

list_achievements

Lists achievement sets and trophies for a specified game or your synced achievement games, with optional per-achievement details and unlock states.

Instructions

Achievements and trophies.

With slug: every achievement set for that game (Steam, PlayStation, Xbox, GOG, RetroAchievements) with your earned count when signed in. include_list=true also returns each achievement (name, description, unlocked state when synced). Without slug: your synced achievement games, newest first. Achievements come from linked store accounts. To track them by hand, use a checkbox Play Records category (set_play_record_category type=checkbox).

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

Input Schema

NameRequiredDescriptionDefault
slugNo
limitNo
max_per_setNo
include_listNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reveal important behavior: data originates from linked store accounts, earned counts and unlocked state only appear when signed in/synced, and results are ordered newest-first without a slug. It omits pagination/truncation behavior despite exposing limit and max_per_set, and doesn't say what happens when no accounts are linked.

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 and dense with usable information; the branching structure around slug is easy to scan. It is slightly fragmented across many short lines and the opening fragment 'Achievements and trophies.' adds little on its own.

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-value detail is not required, and the description covers both modes plus data provenance. The remaining gap is the two undocumented numeric controls (limit, max_per_set) for a tool that can return large achievement sets.

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%, so the description must compensate. It gives real meaning to two of four parameters: slug (per-game mode) and include_list=true (returns each achievement with name, description, unlocked state). limit and max_per_set are left entirely unexplained in both schema and description.

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 names a specific resource (achievements/trophies) and splits into two clearly described modes: with slug = per-game achievement sets across stores, without slug = the user's synced achievement games newest-first. It also points to set_play_record_category for manual tracking, though it doesn't differentiate itself from other list_* siblings such as list_play_records.

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

Usage Guidelines5/5

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

Mode selection is spelled out explicitly ('With slug' / 'Without slug'), which is the primary when-to-use decision for this tool. It also names the alternative path for manual tracking ('use a checkbox Play Records category (set_play_record_category type=checkbox)'), effectively covering when not to use it.

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