Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Item settings

save_item
Destructive

PARTIAL SAVE: writes ONLY the 'Item' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Item catalogue — every consumable, equipment piece, resource, gear or generic inventory entity the player can own. Defines item IDs, names, categories, stack rules, rarities. Referenced by Store SKUs (as contents), Lootbox loot tables, Quest rewards, Craft recipes, and Reward payouts. For premium-tier bundles use Premium; for character entities use Character.

Input Schema

NameRequiredDescriptionDefault
valueYesRoot container for all item catalogs of a title. Source of truth for every ItemID used in the game.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / definitions / ResourceEntryType / enum
      Previous value: -[
-  "Item",
-  "VirtualCurrency",
-  "CryptoCurrency",
-  "Purchase",
-  "RewardedVideoCredit",
-  "PlatformCoin"
-]New value: +[
+  "Item",
+  "VirtualCurrency",
+  "CryptoCurrency",
+  "Purchase",
+  "RewardedVideoCredit",
+  "PlatformCredits"
+]
    • changedInput schema / definitions / ResourceEntryType / x-enum-descriptions
      Previous value: -[
-  "Catalog item. Requires CatalogID, ItemID and Amount.",
-  "In-game (off-chain) virtual currency. Requires CurrencyID and Amount. Looked up in cfg.Currency.VirtualCurrencies.",
-  "On-chain cryptocurrency. Requires CurrencyID and Amount. Looked up in cfg.Currency.CryptoCurrencies.",
-  "Real-money payment in a store. Requires only ProductID (a product from cfg.Purchase.Products); the amount and currency are decided by the store from the SKU price tier. NOT a storable resource and never passes through ResourceService — the money is paid outside before the server learns about it, so the entry is consumed by the receipt check (ExternalPaymentGate) and stripped before the resource operation. Allowed only in Consume and only for Consumable products.",
-  "Rewarded-video credit. One credit equals one verified ad view that can be spent in systems requiring rewarded video (lootbox open, reward double, re-roll, booster). Granted +1 per server-verified view, or as N from milestones/quests/premium perks; spent -1 per gated action.",
-  "Payment in Coin, the PLATFORM currency on the player's iDos Games account. Requires only Amount — the price in whole Coin. Like Purchase it is NOT a player resource and never enters ResourceService: it is settled by PlatformCoinPayment in the same transaction as the grant (buyer charged, author credited). Accepted only by the store (Store.Purchase) for now; allowed only in Consume."
-]New value: +[
+  "Catalog item. Requires CatalogID, ItemID and Amount.",
+  "In-game (off-chain) virtual currency. Requires CurrencyID and Amount. Looked up in cfg.Currency.VirtualCurrencies.",
+  "On-chain cryptocurrency. Requires CurrencyID and Amount. Looked up in cfg.Currency.CryptoCurrencies.",
+  "Real-money payment in a store. Requires only ProductID (a product from cfg.Purchase.Products); the amount and currency are decided by the store from the SKU price tier. NOT a storable resource and never passes through ResourceService — the money is paid outside before the server learns about it, so the entry is consumed by the receipt check (ExternalPaymentGate) and stripped before the resource operation. Allowed only in Consume and only for Consumable products.",
+  "Rewarded-video credit. One credit equals one verified ad view that can be spent in systems requiring rewarded video (lootbox open, reward double, re-roll, booster). Granted +1 per server-verified view, or as N from milestones/quests/premium perks; spent -1 per gated action.",
+  "Payment in Credits, the PLATFORM currency on the player's iDos Games account (players see it as \"Aspis\" — write Aspis in player-facing text). Requires only Amount — the price in whole Credits. Like Purchase it is NOT a player resource and never enters ResourceService: it is settled by PlatformCreditsPayment in the same transaction as the grant (buyer charged, author credited). Accepted only by the store (Store.Purchase) for now; allowed only in Consume."
+]
    • changedInput schema / definitions / ResourceEntryType / x-enumNames
      Previous value: -[
-  "Item",
-  "VirtualCurrency",
-  "CryptoCurrency",
-  "Purchase",
-  "RewardedVideoCredit",
-  "PlatformCoin"
-]New value: +[
+  "Item",
+  "VirtualCurrency",
+  "CryptoCurrency",
+  "Purchase",
+  "RewardedVideoCredit",
+  "PlatformCredits"
+]
  2. Changed3 schema fields changed
    • changedInput schema / definitions / ResourceEntryType / enum
      Previous value: -[
-  "Item",
-  "VirtualCurrency",
-  "CryptoCurrency",
-  "Purchase",
-  "RewardedVideoCredit"
-]New value: +[
+  "Item",
+  "VirtualCurrency",
+  "CryptoCurrency",
+  "Purchase",
+  "RewardedVideoCredit",
+  "PlatformCoin"
+]
    • changedInput schema / definitions / ResourceEntryType / x-enum-descriptions
      Previous value: -[
-  "Catalog item. Requires CatalogID, ItemID and Amount.",
-  "In-game (off-chain) virtual currency. Requires CurrencyID and Amount. Looked up in cfg.Currency.VirtualCurrencies.",
-  "On-chain cryptocurrency. Requires CurrencyID and Amount. Looked up in cfg.Currency.CryptoCurrencies.",
-  "Real-money payment in a store. Requires only ProductID (a product from cfg.Purchase.Products); the amount and currency are decided by the store from the SKU price tier. NOT a storable resource and never passes through ResourceService — the money is paid outside before the server learns about it, so the entry is consumed by the receipt check (ExternalPaymentGate) and stripped before the resource operation. Allowed only in Consume and only for Consumable products.",
-  "Rewarded-video credit. One credit equals one verified ad view that can be spent in systems requiring rewarded video (lootbox open, reward double, re-roll, booster). Granted +1 per server-verified view, or as N from milestones/quests/premium perks; spent -1 per gated action."
-]New value: +[
+  "Catalog item. Requires CatalogID, ItemID and Amount.",
+  "In-game (off-chain) virtual currency. Requires CurrencyID and Amount. Looked up in cfg.Currency.VirtualCurrencies.",
+  "On-chain cryptocurrency. Requires CurrencyID and Amount. Looked up in cfg.Currency.CryptoCurrencies.",
+  "Real-money payment in a store. Requires only ProductID (a product from cfg.Purchase.Products); the amount and currency are decided by the store from the SKU price tier. NOT a storable resource and never passes through ResourceService — the money is paid outside before the server learns about it, so the entry is consumed by the receipt check (ExternalPaymentGate) and stripped before the resource operation. Allowed only in Consume and only for Consumable products.",
+  "Rewarded-video credit. One credit equals one verified ad view that can be spent in systems requiring rewarded video (lootbox open, reward double, re-roll, booster). Granted +1 per server-verified view, or as N from milestones/quests/premium perks; spent -1 per gated action.",
+  "Payment in Coin, the PLATFORM currency on the player's iDos Games account. Requires only Amount — the price in whole Coin. Like Purchase it is NOT a player resource and never enters ResourceService: it is settled by PlatformCoinPayment in the same transaction as the grant (buyer charged, author credited). Accepted only by the store (Store.Purchase) for now; allowed only in Consume."
+]
    • changedInput schema / definitions / ResourceEntryType / x-enumNames
      Previous value: -[
-  "Item",
-  "VirtualCurrency",
-  "CryptoCurrency",
-  "Purchase",
-  "RewardedVideoCredit"
-]New value: +[
+  "Item",
+  "VirtualCurrency",
+  "CryptoCurrency",
+  "Purchase",
+  "RewardedVideoCredit",
+  "PlatformCoin"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description earns credit by narrowing the blast radius: only the 'Item' field is written, all other v1/v2 fields stay untouched. What it does not disclose is the critical merge-vs-replace question — whether the supplied Catalogs object replaces the whole Item field (dropping unlisted catalogs) or merges into it — which is exactly the ambiguity an agent needs resolved before a destructive save.

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?

Front-loads the single most important fact ('PARTIAL SAVE') and follows with domain context, cross-references, and sibling routing. Slightly padded by the enumeration 'every consumable, equipment piece, resource, gear or generic inventory entity', but that breadth aids recognition of what belongs in the catalogue.

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?

No output schema exists, yet the nested model is documented at full coverage and annotations carry the safety profile, so the description only needs to frame purpose and scope — which it does, including downstream references (Store, Lootbox, Quest, Craft, Reward). The remaining gap is write semantics within the Item field (replace vs merge, and what happens to omitted catalogs), which matters given destructiveHint=true.

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 100%, so the schema already explains title_id and the ItemDefinitions/Catalogs structure in depth. The description implicitly maps 'the Item field' to the value parameter but adds no format, merge semantics, or validation detail beyond what the schema states. Baseline 3 applies.

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?

The description opens with a specific verb+resource: 'PARTIAL SAVE: writes ONLY the Item field of TitlePublicConfigurationModel', then defines what that field contains (item catalogues, IDs, stack rules, rarities). It also names the two adjacent siblings it is not ('For premium-tier bundles use Premium; for character entities use Character'), so an agent can distinguish it without opening any schema.

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?

Explicit exclusions are given for the two nearest alternatives (Premium, Character), which is more than most save_* siblings offer. It stops short of stating the positive trigger in one clean sentence ('use this when defining the item catalogue') and offers no prerequisites or read-back guidance, so it is clear but not fully closed.

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

All iDos Games toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources