Skip to main content
Glama

list_wishlist

Retrieve games saved to your Infinite Backlog wishlist, including notes, pre-order status, and favourite flags. Use limit and offset to page through read-only results.

Instructions

List the games on your wishlist with notes, pre-order and favourite flags. Read-only.

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_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the burden; the closing "Read-only" correctly discloses that this is a non-mutating operation, which is genuinely useful. It says nothing about pagination behavior, result ordering, or authentication, all of which matter for a paginated list call.

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 compact sentences with the resource and returned fields front-loaded and the safety profile appended. Nothing is redundant and nothing competes for attention.

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 a simple two-parameter list. Still, the description omits pagination semantics and any hint of how results are scoped, which is the main informational gap for this call.

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%, so the schema gives only bare names and defaults for limit and offset with no meaning attached. The description does not compensate at all — neither pagination nor the interpretation of limit/offset is mentioned, leaving both parameters semantically thin.

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 and resource ("List the games on your wishlist") and enumerates the notable fields returned (notes, pre-order and favourite flags). It does not differentiate itself from siblings such as list_collection or get_list, so an agent must infer the distinction from the name alone.

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 tool lists the user's own wishlist, which an agent can map to intent, but there is no explicit statement of when to prefer it over get_list, list_collection, or list_my_lists. No prerequisites or exclusions are given.

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