Skip to main content
Glama

remove_game_content

Detach DLC and packs from a specific game copy without altering the parent copy; requires confirmation to proceed.

Instructions

Detach DLC/packs from a copy. Needs confirm=true. Does not touch the parent copy itself.

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

Input Schema

NameRequiredDescriptionDefault
namesYes
confirmNo
parent_slugYes
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior: this is a detaching mutation, it is gated behind confirm=true, and its blast radius excludes the parent copy. It does not say whether detaching is reversible, what happens to files/records on the detached content, whether confirm=false aborts or silently no-ops, or what permissions are needed.

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, front-loaded with the operation, then the gating requirement, then the scope boundary. No filler or redundancy.

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 the safety boundary is stated. Still, for a four-parameter mutation with zero annotation and zero schema-doc coverage, the definition leaves required inputs like names and parent_slug undefined and never clarifies what collection_id does.

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 explain the four parameters and largely does not. It only conveys the semantics of confirm (must be true); names, parent_slug, and collection_id receive no meaning, format, or expected-value guidance beyond their bare titles.

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?

Names a specific verb and resource: 'Detach DLC/packs from a copy.' The closing clause 'Does not touch the parent copy itself' separates it from the destructive sibling delete_game_copy and from add_game_content, so an agent can pick the right tool without opening a schema.

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 prerequisite 'Needs confirm=true' is a concrete invocation condition, and the parent-copy clause implies when this is preferable to deleting a copy. However, there is no explicit 'use this instead of X when...' routing and no statement of when the tool is inappropriate.

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