Skip to main content
Glama

set_game_details

Update a game copy's platform, ownership, region, edition, digital status, and lending details, or clear selected fields when collection records need correction.

Instructions

Basic info on one copy: platform, ownership (owned, household, subscription, borrowed, rented, unlicensed, formerlyOwned, lentOut, other), digital true/false, region (pal/EU, ntsc-u/US, ntsc-j/JP, ntsc-c, australia, brazil, asia, korea, other), edition (slug of an edition from list_related_content), lent_to, borrowed_from. clear_fields: edition, region, lent_to, borrowed_from.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
regionNo
digitalNo
lent_toNo
platformNo
ownershipNo
clear_fieldsNo
edition_slugNo
borrowed_fromNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it never states that this is a mutation, whether omitted or empty-string parameters leave values unchanged, how clear_fields should be formatted for multiple fields, or what collection_id does. It does add useful context by documenting the ownership and region vocabularies and by pointing edition at list_related_content, but core mutation semantics are undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is a single dense field dump with no wasted prose, but it is not front-loaded with an action statement and reads as an unstructured enumeration of value lists. Splitting 'what it does' from 'accepted values' would materially improve scanning.

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?

For a 10-parameter mutation tool, incompleteness remains: the update/clear semantics, slug, and collection_id are undocumented, and no annotations exist to fill the safety gap. An output schema exists, so return values need not be explained, but the mutation contract itself is under-specified.

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%, yet the description supplies value vocabularies for ownership, region and digital, and links edition to list_related_content, which is real added meaning. However, slug and collection_id are never described at all, and the description's 'edition' does not match the schema's 'edition_slug', so mapping is left ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Basic info on one copy') and enumerates the fields it covers, but never states a verb or that this writes/updates the copy's detail record. An agent must infer mutation from the tool name 'set_game_details' and the presence of 'clear_fields'. It is on-topic but not stated as a specific verb+resource operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or routing guidance is given. Sibling tools such as set_game_acquisition, set_game_progress and add_game_platform_copy overlap in domain, yet the description never says this tool is for platform/ownership/region/edition/loan state only, leaving the agent to guess from the field list.

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