Skip to main content
Glama

add_to_wishlist

Adds a game to your Infinite Backlog wishlist and optionally sets notes or preorder status, updating the entry if the game is already listed.

Instructions

Add a game to your wishlist. Optional notes and preorder ("true"/"false"; empty keeps the current value), applied also when the game is already on it.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
notesNo
preorderNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of explaining this write operation. It usefully discloses update-like behavior for existing entries and preservation of the current value when an empty value is supplied, but it does not address authorization, failures, or defaults when creating a new wishlist entry.

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?

Two compact sentences front-load the operation and then cover parameter and existing-entry behavior without filler. The second sentence is grammatically compressed, making the exact scope of "empty keeps the current value" and "applied also" somewhat harder to parse.

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?

For a flat three-parameter tool with an output schema, the description covers the core operation and important optional-field and existing-entry behavior without needing to explain the response. Its main remaining invocation gaps are slug acquisition or format and operational prerequisites such as authentication.

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?

Despite 0% schema description coverage, it explains that notes and preorder are optional, restricts preorder to the strings "true" and "false", and describes empty-value behavior. The required slug receives no semantic help, such as its format, an example, or where to obtain it, so compensation for the undocumented schema is incomplete.

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 opening sentence states a specific action and resource: adding a game to the user's wishlist. The wishlist scope distinguishes it conceptually from collection tools, but the description does not explicitly contrast it with add_game_to_collection or another sibling.

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?

It provides a concrete use case and explicitly covers the scenario where the game is already on the wishlist, clarifying that the optional fields still apply. It offers no when-not guidance or routing to relevant alternatives such as collection or wishlist-removal tools.

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