Skip to main content
Glama

add_game_platform_copy

Add another platform copy of a game you already own so you can track separate progress, acquisition details, and play records.

Instructions

Add another copy of a game you already own, on another platform (its own progress, acquisition and play records).

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

Input Schema

NameRequiredDescriptionDefault
slugYes
submitNo
digitalNo
platformYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • removedInput schema / properties / collection_id
      Removed value: -{
      -  "default": "",
      -  "title": "Collection Id",
      -  "type": "string"
      -}
    • removedInput schema / properties / digital / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / digital / default
      Previous value: -nullNew value: +false
    • addedInput schema / properties / digital / type
      Added value: +"boolean"
    • removedInput schema / properties / platform / default
      Removed value: -""
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 3000,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slug"
      -]New value: +[
      +  "slug",
      +  "platform"
      +]
  2. First observedv1.0.1

TDQS

A3.6/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 behavioral burden. The parenthetical is genuinely useful: it discloses that the new copy gets independent progress, acquisition and play records rather than sharing the original's. However, nothing is said about duplicate handling, required ownership/permissions, or whether the operation is reversible, which are the critical unknowns for a write operation.

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?

A single front-loaded sentence with zero filler; the parenthetical adds density rather than padding. Nothing can be removed without losing meaning.

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 explained, and the description conveys the core mental model of what a platform copy is. The remaining gap is parameter-level: with 0% schema coverage, two of the four parameters are undocumented anywhere.

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% — the parameters carry only bare titles — so the description must compensate. It implicitly covers slug ('a game you already own') and platform, but says nothing about 'digital' or 'submit', which are the two ambiguous flags an agent could easily get wrong.

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 gives a specific verb and object ('Add another copy of a game') plus the scoping condition ('on another platform'), which is enough to separate it from content/play-session siblings like add_game_content or add_play_session. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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 implied by the precondition 'a game you already own' — an agent knows this is for expanding an existing library entry, not for first-time acquisition. There is no explicit when-not guidance (e.g., what to do if the platform copy already exists) and no named alternative such as copy_play_records.

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