Skip to main content
Glama

add_game_content

Attach DLC, expansions, packs, or add-ons to a copy you own by matching related titles or game IDs. Skips already-attached items and optionally sets DLC completion.

Instructions

Attach DLC, expansions, packs or add-ons to a copy you own. names: one title, a JSON array, or one title per line (game ids also work). Matches against the game's related content; already-attached items are skipped. completion (DLC only) sets their completion. platform/digital are ignored (they belong to the parent 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": {
      "parent_slug": "<parent_slug>",
      "names": "<names>"
    },
    "name": "add_game_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes
digitalNo
wait_msNo
platformNo
completionNo
parent_slugYes
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / completion
      Added value: +{
      +  "default": "",
      +  "title": "Completion",
      +  "type": "string"
      +}
    • changedInput schema / properties / wait_ms / default
      Previous value: -3500New value: +0
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose real behavior: names are matched 'against the game's related content' and 'already-attached items are skipped' (idempotent, no duplicates), and completion applies only to DLC. It still omits what happens to unmatched names, whether partial matches add anything, and any permission or return behavior.

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?

The core action and parent scope lead, followed by input formats and then the caveats; every sentence carries information. The telegraphic fragments ('names: ...', 'completion (DLC only) sets their completion') read as notes rather than prose and cost a little readability.

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 needn't be explained, and the matching/skip semantics are covered. For a 7-parameter mutation tool with zero schema descriptions, though, three parameters (collection_id, wait_ms, parent_slug) and the failure case for non-matching names remain unaddressed.

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 coverage is 0%, so the description must compensate, and it does for the hardest parameter: 'names' accepts one title, a JSON array, or one title per line, and game ids work. It also disambiguates 'completion' (DLC only) and neutralizes platform/digital. But parent_slug, collection_id and wait_ms carry no meaning in either the schema or the description.

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 ('Attach') and a specific resource class ('DLC, expansions, packs or add-ons') with scope ('to a copy you own'), which is far more than restating the name. It never names the inverse sibling remove_game_content, so differentiation is left implicit 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear ('to a copy you own' with a parent_slug parent) and it explicitly steers the agent away from the wrong params: platform/digital 'are ignored (they belong to the parent copy)', which implies the sibling that handles them. No alternative tool is named by name and no error/rejection scenario is described.

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