Skip to main content
Glama

delete_game_copy

Delete a single game copy from a collection, including its linked progress, acquisition, and play records. Requires a collection ID and explicit confirmation.

Instructions

Delete one copy from your collection, with its progress, acquisition and play records link. Needs collection_id and 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": "delete_game_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / collection_id / default
      Added value: +""
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 3000,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slug",
      -  "collection_id"
      -]New value: +[
      +  "slug"
      +]
  2. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the important destructive footprint: the copy plus linked progress, acquisition and play records are removed. It omits whether this is irreversible, whether it can be undone, and what authorization or confirmation semantics govern the call beyond the confirm flag.

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?

One front-loaded sentence with the destructive scope first and prerequisites last, which is the right ordering. The clause 'with its progress, acquisition and play records link' is grammatically tangled and slightly obscures what exactly is deleted.

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 here, and the cascade scope is covered. Still, for an uncovered-annotation mutation tool, the description leaves out irreversibility and fails to correctly describe which parameters are actually mandatory.

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 description must compensate, and it partially does by explaining the confirm gate. However it never mentions 'slug' — the only required parameter — and asserts that collection_id is needed, while the schema marks it optional with an empty default. That mismatch will mislead an agent about what to supply.

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 — 'Delete one copy from your collection' — with an explicit cascade scope (progress, acquisition, play records link). This is clearly distinct from siblings like delete_game_review or delete_list, though it never names an alternative.

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?

It gives invocation prerequisites ('Needs collection_id and confirm=true'), which is a form of usage guidance, but gives no when-to-use/when-not context and no alternatives for removing a copy versus, say, deleting a review. Because the requiredness claim conflicts with the schema (see parameter score), the guidance is only partially trustworthy.

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