Skip to main content
Glama

set_game_acquisition

Set or clear acquisition details and physical condition for one game copy in Infinite Backlog, including source, date, price, state, and grading.

Instructions

Acquisition and condition on one copy. acquisition: purchase, subscription, gift, trade, keyBundle, promotionalCopy, reviewCopy, free, freeToPlay. source: store or shop name (matched to IB's purchase places). date YYYY-MM-DD. amount and additional_costs are normal prices in your IB currency (9.99); the tool stores them the way IB does. digital_service: steam, epicGameStore, gog, psn, xboxLive, nintendoEShop, ... state new/used. condition cib/incomplete/loose/sealed. condition_game/box/manual: mint/good/acceptable/poor/missing/na. clear_fields empties any of those names.

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_acquisition"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
slugYes
notesNo
stateNo
amountNo
sourceNo
conditionNo
acquisitionNo
clear_fieldsNo
collection_idNo
condition_boxNo
condition_gameNo
digital_serviceNo
additional_costsNo
condition_manualNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.1.0
    • removedInput schema / properties / additional_cost
      Removed value: -{
      -  "default": "",
      -  "title": "Additional Cost",
      -  "type": "string"
      -}
    • addedInput schema / properties / additional_costs
      Added value: +{
      +  "default": "",
      +  "title": "Additional Costs",
      +  "type": "string"
      +}
    • addedInput schema / properties / condition
      Added value: +{
      +  "default": "",
      +  "title": "Condition",
      +  "type": "string"
      +}
    • addedInput schema / properties / condition_box
      Added value: +{
      +  "default": "",
      +  "title": "Condition Box",
      +  "type": "string"
      +}
    • addedInput schema / properties / condition_game
      Added value: +{
      +  "default": "",
      +  "title": "Condition Game",
      +  "type": "string"
      +}
    • addedInput schema / properties / condition_manual
      Added value: +{
      +  "default": "",
      +  "title": "Condition Manual",
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "default": "",
      +  "title": "State",
      +  "type": "string"
      +}
    • removedInput schema / properties / subscription
      Removed value: -{
      -  "default": "",
      -  "title": "Subscription",
      -  "type": "string"
      -}
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 3000,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
  2. First observedv1.0.1

TDQS

B3.1/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 some behavior: prices are stored "the way IB does" (implying normalization/currency assumptions), source values are matched to IB's purchase places (implying fuzzy resolution), and clear_fields empties named fields. It omits whether unmentioned fields are preserved or overwritten, permission requirements, and what happens on unrecognized enum values.

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?

Every clause carries parameter information with no filler, and the size is proportionate to a 15-parameter tool. The telegraphic, unbroken run of value lists hurts parseability somewhat, but nothing is redundant.

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 most value-bearing parameters are covered. However, for a 15-parameter mutation tool with zero annotations, the missing hints on overwrite semantics, the role of slug/collection_id, and failure behavior leave real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with 15 parameters and no enums, so the description must compensate, and it largely does: it enumerates allowed values for acquisition, digital_service, state, condition, and condition_game/box/manual, gives the date format, explains amount/additional_costs as normalized currency, and clarifies clear_fields. Slug, notes, and collection_id remain undocumented.

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?

"Acquisition and condition on one copy" conveys that this sets purchase/condition data on a single copy, but it is close to a restatement of the tool name with no clear verb (set vs. add vs. update) and no differentiation from siblings such as add_game_platform_copy or delete_game_copy. An agent can guess the effect but not confidently distinguish it from adjacent copy-mutation tools.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The enumerated value lists describe what to pass, not when this tool is the right choice over adding a copy or editing game details, so an agent must infer usage entirely.

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