Skip to main content
Glama

list_related_content

Lists DLC, expansions, add-ons, editions, bundles, remakes, and other related games for a game slug, grouped by collection category; uses public data with no login required.

Instructions

List DLC, expansions, packs/add-ons, editions, bundles, remakes and other related games.

Grouped the way the collection editor uses them: dlc (completion tracked), addons (packs, mods, updates), editions (bundles) and other. Public data; no login needed.

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": {
      "game_slug": "<game_slug>"
    },
    "name": "list_related_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_msNo
game_slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / wait_ms / default
      Previous value: -3000New value: +0
  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 that data is public and requires no login plus how results are bucketed (dlc with completion tracking, addons, editions, other). It says nothing about pagination, result size, error behavior for unknown slugs, or why the wait_ms parameter exists.

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?

Three short sentences, front-loaded with the enumerated content types before the grouping detail and the access note. Nearly every phrase earns its place, though the category breakdown partially duplicates what the output schema likely conveys.

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-value documentation is not required, and the access note covers auth. However, for a two-parameter tool with zero schema coverage and no annotations, leaving wait_ms entirely unexplained is a meaningful completeness gap.

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 two parameters and does not. game_slug is inferable from its name, but wait_ms is completely undocumented — neither its purpose (presumably a delay/retry wait) nor its units or default are addressed anywhere.

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 opens with a specific verb and resource ("List DLC, expansions, packs/add-ons, editions, bundles, remakes and other related games") and enumerates exactly what counts as related content. It is clearly distinguishable from collection-management siblings like list_collection or get_game, though it never names an alternative explicitly.

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 only implied: it takes a game slug and returns the associated DLC/editions, so an agent can infer it should be called when enumerating a game's extended offerings. There is no explicit when-to-use versus when-to-use-something-else guidance, and no mention of how this relates to add_game_content or list_collection_content_menus.

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