Skip to main content
Glama

remove_from_wishlist

Remove a game from your wishlist by slug, with a required confirm=true flag to prevent accidental deletions.

Instructions

Remove a game from your wishlist. Needs confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.4/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 confirmation requirement, which is the key safety behavior for a destructive removal. It does not state what happens when confirm is false/omitted (silent no-op vs. error), whether removal is reversible, or whether auth is required.

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 short sentences, front-loaded with the action and followed by the prerequisite; nothing is wasted. The second sentence is telegraphic ('Needs confirm=true') but still readable in context.

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 no explanation, and for a simple two-parameter mutation the description covers the action and the confirmation gate. It leaves the slug parameter undefined and gives no failure-mode behavior, which for a destructive operation with zero annotations is a notable gap.

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 does explain the semantics of 'confirm' (must be true) beyond the schema's bare default of false, which is genuinely useful. The required 'slug' parameter is left entirely undefined, and the description does not say what entity the slug identifies or what a valid slug looks like.

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 (remove) and resource (game from your wishlist), which cleanly distinguishes it from sibling add_to_wishlist and list_wishlist. It stops short of naming the inverse tool explicitly, but the operation itself is unambiguous.

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 line 'Needs confirm=true' communicates a hard prerequisite for invocation, which is real usage context. However, there is no guidance on when to prefer this over related tools (e.g. remove_game_content, delete_game_copy) or any warning about the consequences of calling it.

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