Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Premium settings

save_premium
Destructive

PARTIAL SAVE: writes ONLY the 'Premium' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Premium offerings catalogue — paid subscriptions, premium passes, real-money bundle skus, supporter tiers. Distinct from Store (regular in-game shop with virtual-currency prices) and from DealOffer (limited-time promotional offers). Use this specifically for monetization tiers / IAP that grant ongoing benefits.

Input Schema

NameRequiredDescriptionDefault
valueYesRoot container of premium subscriptions / premium passes for the title. Holds a dictionary of definitions keyed by PremiumID. Distinct from Store (in-game shop with virtual-currency prices) and from DealOffer (time-limited promotions).
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.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered, and the description usefully narrows the blast radius by stating all other v1/v2 fields stay untouched. What it does not disclose is that the Premium field itself is replaced wholesale (existing definitions not present in the payload presumably vanish) or that this requires write auth on the title — a real gap for 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-loaded with the most important fact — that this is a partial save of one field — and then the domain and the sibling distinctions. Slightly redundant: the catalogue list of premium offerings largely restates the schema's own description of the value container, and the final 'Use this specifically…' sentence could merge with the distinction sentence.

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 2-parameter save with full schema coverage and no output schema, the description covers purpose, scope of the write, and sibling routing. It falls just short on replace-vs-merge semantics for the existing Premium definitions, which is the one thing an agent could get wrong when calling a destructive save.

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% and the nested PremiumDefinition tree is documented in detail in the schema itself, so the baseline of 3 applies. The description mirrors the schema's own Store/DealOffer disambiguation but adds no new meaning about how title_id or value should be formed or keyed by PremiumID.

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 and scope ('PARTIAL SAVE: writes ONLY the "Premium" field of TitlePublicConfigurationModel') and enumerates the domain contents (subscriptions, premium passes, real-money SKUs, supporter tiers). It also names the two sibling tools it is not — Store and DealOffer — so the agent can pick 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 Guidelines5/5

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

Explicit exclusions are given ('Distinct from Store … and from DealOffer') along with a positive selection rule ('Use this specifically for monetization tiers / IAP that grant ongoing benefits'). Both the when and the when-not are stated, which is exactly what separates it from save_store and save_deal_offer.

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