Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save AI settings

save_ai
Destructive

PARTIAL SAVE: writes ONLY the 'AI' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. InApp AI generation features of the title - what a PLAYER can generate at runtime through the engine (text/NPC chat, images, video, speech, music, 3D). Enabled is the master switch; Features maps a stable FeatureKey (no '.' or '$') to one feature: its Modality, a Model = the id of a MODE (Text: an AI Coder mode such as "standard") or a TIER (media: an asset generation tier such as "image-balanced") - list the usable ones, with what the publisher's plan allows, with the dashboard action GetInAppAIModels (Text features that AllowImages need a mode that AcceptsImages), Behavior defaults per modality (no platform caps: MaxTokens is bounded only by what the mode's model can produce), Safety prompt checks, an audience Gate (SegmentGate), a Schedule (ScheduleSpec), per-player Limits (LimitSpec) and the in-game PriceOptions the PLAYER pays (in-game resources and/or ONE store purchase per generation - a Purchase entry in the option's base price; never inside PremiumTiers, never two per option). Each generation is charged to the PUBLISHER's credits by the engine at the model's price; per-title spend caps (in credits) live in the PRIVATE config (InAppAIBudget), not here. Server-only section: never sent to the game client or the CDN.

Input Schema

NameRequiredDescriptionDefault
valueYesInApp AI generation features of the title. Bound to cfg.AI. A PLAYER triggers generation at runtime through the engine; models and prices come from the platform model registry, the provider is OpenRouter (3D: Meshy), keys are platform keys. Each generation is charged to the PUBLISHER's credits at the model's price in the same request; the player additionally pays per feature (PriceOptions: in-game resources and/or one store purchase). Server-only section: never projected to the client config or the CDN.
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. Changed1 schema field changed
    • addedInput schema / definitions / AIBehaviorSettings / properties / ShareIdenticalResults
      Added value: +{
+  "description": "Audio (TTS): reuse the ready file when the same text was already voiced with the same voice in this title — no new generation, no credits, free for the player.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
  4. Changed3 schema fields changed
    • changedInput schema / definitions / EventTokenSourceType / enum
      Previous value: -[
-  "BoardTileLanding",
-  "BoardPassStart",
-  "BoardAttack",
-  "BoardRaid",
-  "BoardBuild",
-  "BoardStageComplete",
-  "BoardSpecialComplete",
-  "QuestComplete",
-  "StorePurchase",
-  "DailyLogin",
-  "ReferralInvite",
-  "MilestoneReward",
-  "CustomAction",
-  "LeaderboardRankReward",
-  "MarketplaceSell",
-  "MarketplaceBuy",
-  "CurrencySpent",
-  "LootboxOpened",
-  "IapPurchase",
-  "CryptoDeposit",
-  "CryptoWithdraw",
-  "CryptoSpent",
-  "CurrencyEarned",
-  "CryptoEarned"
-]New value: +[
+  "BoardTileLanding",
+  "BoardPassStart",
+  "BoardAttack",
+  "BoardRaid",
+  "BoardBuild",
+  "BoardStageComplete",
+  "BoardSpecialComplete",
+  "QuestComplete",
+  "StorePurchase",
+  "DailyLogin",
+  "ReferralInvite",
+  "MilestoneReward",
+  "CustomAction",
+  "LeaderboardRankReward",
+  "MarketplaceSell",
+  "MarketplaceBuy",
+  "CurrencySpent",
+  "LootboxOpened",
+  "IapPurchase",
+  "CryptoDeposit",
+  "CryptoWithdraw",
+  "CryptoSpent",
+  "CurrencyEarned",
+  "CryptoEarned",
+  "ClientScore"
+]
    • changedInput schema / definitions / EventTokenSourceType / x-enum-descriptions
      Previous value: -[
-  "Landing on an EventToken tile on the board.",
-  "Passing start (GO) on the board.",
-  "Successful board attack.",
-  "Successful board raid.",
-  "Building or repairing a structure on the board.",
-  "Completing a board stage.",
-  "Completing a board Special mode — either via Instant choice or via Claim after the Timed window. Post-resolution source (mirrors BoardAttack/BoardRaid): fires at the final Special reward grant, separately from BoardTileLanding (which fires on the actual tile landing during Roll).",
-  "Completing a quest.",
-  "Store purchase.",
-  "Daily login.",
-  "Referral invite.",
-  "Token grant as a reward for a milestone or streak in another event. Server-only source — the client cannot invoke it directly.",
-  "Arbitrary action — the developer calls the server API with ActionName in Params.",
-  null,
-  "Marketplace (v2) sale — deal settlement on the seller side. Server-only source. Filter Params: CatalogID / ItemID / OfferType.",
-  "Marketplace (v2) purchase — deal settlement on the buyer side. Server-only source. Filter Params: CatalogID / ItemID / OfferType.",
-  "In-game currency spend — any scenario where a resource operation actually consumed currency. Server-only source. The multiplier equals the amount spent. Filter Params: CurrencyID.",
-  "Opening a lootbox/chest. Server-only source. The multiplier equals how many boxes were opened in the call. Filter Params: LootboxID.",
-  "Real-money store purchase (IAP). Server-only source: fired in PurchaseV2 AFTER the receipt is verified and rewards are granted. The multiplier equals the number of product units granted. Filter Params: ProductID, Store. Deliberately separate from StorePurchase, which covers in-game currency spending.",
-  "Crypto deposit credited to the in-game balance. Multiplier is 1 (one operation). Filter Params: CurrencyID, NetworkID.",
-  "Crypto withdrawal CONFIRMED on chain. Multiplier is 1 (one operation). Filter Params: CurrencyID, NetworkID.",
-  "Spending crypto currency in-game. The multiplier equals the amount spent. Filter Params: CurrencyID.",
-  "In-game currency GRANT — mirror of CurrencySpent. The multiplier equals the amount granted, so ScaleWithRollMultiplier picks the meaning: \"earn N currency\" or \"receive currency N times\". Filter Params: CurrencyID and Origin (\"Gameplay\" | \"RewardClaim\"), the latter separating gameplay earnings from reward payouts — without it a goal like \"earn N\" would be closed by another quest's reward.",
-  "CRYPTO currency GRANT in-game (wallet deposits are NOT included — that is CryptoDeposit). The multiplier equals the amount granted. Filter Params: CurrencyID, Origin."
-]New value: +[
+  "Landing on an EventToken tile on the board.",
+  "Passing start (GO) on the board.",
+  "Successful board attack.",
+  "Successful board raid.",
+  "Building or repairing a structure on the board.",
+  "Completing a board stage.",
+  "Completing a board Special mode — either via Instant choice or via Claim after the Timed window. Post-resolution source (mirrors BoardAttack/BoardRaid): fires at the final Special reward grant, separately from BoardTileLanding (which fires on the actual tile landing during Roll).",
+  "Completing a quest.",
+  "Store purchase.",
+  "Daily login.",
+  "Referral invite.",
+  "Token grant as a reward for a milestone or streak in another event. Server-only source — the client cannot invoke it directly.",
+  "Arbitrary action — the developer calls the server API with ActionName in Params.",
+  null,
+  "Marketplace (v2) sale — deal settlement on the seller side. Server-only source. Filter Params: CatalogID / ItemID / OfferType.",
+  "Marketplace (v2) purchase — deal settlement on the buyer side. Server-only source. Filter Params: CatalogID / ItemID / OfferType.",
+  "In-game currency spend — any scenario where a resource operation actually consumed currency. Server-only source. The multiplier equals the amount spent. Filter Params: CurrencyID.",
+  "Opening a lootbox/chest. Server-only source. The multiplier equals how many boxes were opened in the call. Filter Params: LootboxID.",
+  "Real-money store purchase (IAP). Server-only source: fired in PurchaseV2 AFTER the receipt is verified and rewards are granted. The multiplier equals the number of product units granted. Filter Params: ProductID, Store. Deliberately separate from StorePurchase, which covers in-game currency spending.",
+  "Crypto deposit credited to the in-game balance. Multiplier is 1 (one operation). Filter Params: CurrencyID, NetworkID.",
+  "Crypto withdrawal CONFIRMED on chain. Multiplier is 1 (one operation). Filter Params: CurrencyID, NetworkID.",
+  "Spending crypto currency in-game. The multiplier equals the amount spent. Filter Params: CurrencyID.",
+  "In-game currency GRANT — mirror of CurrencySpent. The multiplier equals the amount granted, so ScaleWithRollMultiplier picks the meaning: \"earn N currency\" or \"receive currency N times\". Filter Params: CurrencyID and Origin (\"Gameplay\" | \"RewardClaim\"), the latter separating gameplay earnings from reward payouts — without it a goal like \"earn N\" would be closed by another quest's reward.",
+  "CRYPTO currency GRANT in-game (wallet deposits are NOT included — that is CryptoDeposit). The multiplier equals the amount granted. Filter Params: CurrencyID, Origin.",
+  "Leaderboard ScoreSources only: the board accepts the NUMBER the game submits itself (SubmitScore / SubmitScoresBatch). Not an event — it grants nothing and matches nothing, it only allows. Without it the board refuses a score from the game: an empty ScoreSources list means the board is not set up. Caps live in Limits: PerActivationCap = max score of ONE submission, DailyCap / DailyWeightCap = submissions / total score per UTC day, CooldownSeconds, MaxPerWindow + WindowSeconds, TotalCap = submissions for all time. A submission over a cap is refused, not trimmed. BaseWeight is not read. Set caps the game can really reach: the client is not trusted, they are the only limit on a forged score."
+]
    • changedInput schema / definitions / EventTokenSourceType / x-enumNames
      Previous value: -[
-  "BoardTileLanding",
-  "BoardPassStart",
-  "BoardAttack",
-  "BoardRaid",
-  "BoardBuild",
-  "BoardStageComplete",
-  "BoardSpecialComplete",
-  "QuestComplete",
-  "StorePurchase",
-  "DailyLogin",
-  "ReferralInvite",
-  "MilestoneReward",
-  "CustomAction",
-  "LeaderboardRankReward",
-  "MarketplaceSell",
-  "MarketplaceBuy",
-  "CurrencySpent",
-  "LootboxOpened",
-  "IapPurchase",
-  "CryptoDeposit",
-  "CryptoWithdraw",
-  "CryptoSpent",
-  "CurrencyEarned",
-  "CryptoEarned"
-]New value: +[
+  "BoardTileLanding",
+  "BoardPassStart",
+  "BoardAttack",
+  "BoardRaid",
+  "BoardBuild",
+  "BoardStageComplete",
+  "BoardSpecialComplete",
+  "QuestComplete",
+  "StorePurchase",
+  "DailyLogin",
+  "ReferralInvite",
+  "MilestoneReward",
+  "CustomAction",
+  "LeaderboardRankReward",
+  "MarketplaceSell",
+  "MarketplaceBuy",
+  "CurrencySpent",
+  "LootboxOpened",
+  "IapPurchase",
+  "CryptoDeposit",
+  "CryptoWithdraw",
+  "CryptoSpent",
+  "CurrencyEarned",
+  "CryptoEarned",
+  "ClientScore"
+]
  5. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the destructive annotation, it discloses that only the AI field is overwritten while other fields remain untouched, that the section is server-only and never sent to the client or CDN, that generation costs are charged to publisher credits, and that spend caps live in the private config. These are important behavioral constraints for a destructive save tool.

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 critical partial-save constraint is front-loaded, which is good. However, the middle sentence is an extremely dense run-on covering many nested concepts, making the description harder to parse than necessary for an agent.

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 complex nested save tool with no output schema, the description covers scope, server-only visibility, model selection, pricing, limits, and the fact that per-title budget caps are private elsewhere. It still omits permissions, validation/error behavior, and concurrency considerations, so it is strong but not fully complete.

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 coverage is 100%, so the nested schema already documents title_id and value extensively. The description adds useful cross-system context about publisher credits, private budget caps, and PriceOptions restrictions, but much of it repeats schema descriptions rather than adding new per-parameter semantics.

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 opening sentence states a precise verb and scope: it is a partial save that writes only the AI field of TitlePublicConfigurationModel and leaves all other v1/v2 fields untouched. This distinguishes it from a generic title save without needing the sibling 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?

It clearly establishes the usage context as a partial save limited to the AI field and mentions GetInAppAIModels for discovering usable model ids. However, it does not explicitly name alternatives such as save_title_data or state when not to use this tool.

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