Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Experiment settings

save_experiment
Destructive

PARTIAL SAVE: writes ONLY the 'Experiment' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. A/B experiments — variant definitions with weighted allocation, audience gate (SegmentGate) and schedule (ScheduleSpec). Players are assigned to a variant by a stable hash; variant Params carry inline config overrides. Used to test config changes against measurable cohorts.

Input Schema

NameRequiredDescriptionDefault
valueYesRoot block of the A/B experiment system. An experiment = who (Gate: SegmentGate) + when (Schedule: ScheduleSpec) + a random sticky split into variants. Variant assignment is deterministic by a STABLE hash (ExperimentAssigner), NOT SecureRandom, so it is reproducible and stable across sessions. Consumed as a SegmentGate.Experiment condition, so A/B works in every module already using SegmentGate.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observed

TDQS

A3.9/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, so the write/mutation profile is known. The description adds genuinely useful scope information beyond that: the write is partial (only the Experiment field), all other v1/v2 fields are preserved, and assignment is by a stable hash rather than random. It does not cover idempotency, auth requirements, or error behavior.

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?

Three sentences, front-loaded with the most decision-relevant fact (PARTIAL SAVE) before the domain explanation. No filler, though the third sentence is more background color than actionable instruction.

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 destructive two-parameter write with no output schema, the description supplies the critical scoping fact (only Experiment is written, other fields untouched) plus the assignment semantics. Return value need not be explained absent an output schema. Missing only auth/permission expectations and whether title_id must already exist.

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 definitions are extensively self-documented, so the schema carries the parameter burden. The description adds only light framing ("variant definitions with weighted allocation, audience gate (SegmentGate) and schedule (ScheduleSpec)", "variant Params carry inline config overrides") that largely restates the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource (save experiment settings) and immediately qualifies the write scope: "PARTIAL SAVE: writes ONLY the 'Experiment' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched." This cleanly distinguishes it from get_experiment and from the other save_* tools that write whole config blocks.

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

Usage Guidelines3/5

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

The closing sentence "Used to test config changes against measurable cohorts" implies the purpose, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g. get_experiment for reading, or which other save_* tool to use for non-experiment config). Usage is inferable but not stated.

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