Skip to main content
Glama

add_game_to_collection

Add a game to a collection as one copy on one platform; duplicate copies on the same platform are refused unless explicitly allowed. Use a separate platform-copy action for another platform.

Instructions

Add a game to your collection (one copy on one platform). Refuses a second copy on the same platform unless allow_duplicate=true. For another platform use add_game_platform_copy.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
statusNounplayed
digitalNo
platformNo
allow_duplicateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does disclose the key side effect: silent deduplication on the same platform with an explicit override flag. It does not say whether an unknown slug creates a new game entry or fails, nor whether the write requires any privileges, so a small gap remains.

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?

Three short sentences, each carrying distinct information — scope, refusal rule, alternative tool — with the defining constraint front-loaded. No redundant restatement of the tool name or title.

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 described, and the core duplicate-handling policy is covered. The remaining shortfall is the undocumented status/digital parameters, which an agent would have to guess at for anything beyond a bare add.

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 explains the meaning of platform (the copy's platform), allow_duplicate (bypass the duplicate refusal), and implicitly slug (which game), but says nothing about status or digital, leaving two of five parameters without semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Add a game to your collection') and immediately constrains the unit of operation to 'one copy on one platform', which cleanly separates it from add_game_platform_copy. An agent can distinguish the two tools without opening either schema.

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?

Gives an explicit refusal condition ('Refuses a second copy on the same platform') plus the escape hatch ('unless allow_duplicate=true') and names the alternative for the other case ('For another platform use add_game_platform_copy'). When-to-use, when-not-to-use, and the alternative are all stated.

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