Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Leaderboard settings

save_leaderboard
Destructive

PARTIAL SAVE: writes ONLY the 'Leaderboard' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Leaderboard definitions — name, ranking metric (score type), reset cadence (daily/weekly/seasonal/perpetual), tier-based rewards, eligibility rules. Use for pure player-vs-player ranking. For collaborative team goals use CoopEvent.

Input Schema

NameRequiredDescriptionDefault
valueYesNew value for the Leaderboard field.
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. Changed4 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"
+]
    • changedInput schema / definitions / LeaderboardDefinition / properties / ScoreSources / description
      Previous value: -"Server-side score sources. A leaderboard accrues score automatically from game events (board landings/attacks/raids/builds/stages, plus Quest/Store/CustomAction, etc.) matching these sources, instead of relying solely on client SubmitScore. Empty = client-submit only. Uses the unified TriggerSource (BaseWeight = score per trigger; Limits left null — leaderboards apply no anti-farm caps). Empty = client-submit only."New value: +"Where the score comes from. Event sources: the leaderboard accrues score automatically from game events (board landings/attacks/raids/builds/stages, plus Quest/Store/CustomAction, etc.) matching them (BaseWeight = score per trigger; Limits are not applied to event sources). ClientScore: the board accepts the NUMBER the game submits itself (SubmitScore / SubmitScoresBatch), capped by that entry's Limits (PerActivationCap = max per submission, DailyCap, DailyWeightCap, CooldownSeconds, MaxPerWindow + WindowSeconds, TotalCap). Without a ClientScore entry the board refuses every score from the game — an empty list means the board is not set up. Leaderboard tokens granted by rewards (board tiles, quests, store) score the board on the server regardless of this list."
  4. First observed

TDQS

A4.2/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; the description adds the crucial qualifier that destruction is scoped to one field and sibling fields are preserved, which meaningfully narrows the annotation's implied blast radius. It stops short of saying whether the supplied Definitions dictionary replaces or merges the existing set — the one behavioral question a destructive save raises.

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?

Roughly four tight sentences with no filler, and the most important fact — PARTIAL SAVE — is front-loaded in caps. Minor deduction: 'daily/weekly/seasonal/perpetual' loosely paraphrases the actual reset enum (Hourly/Daily/Weekly/Monthly/Yearly/FixedInterval/Never), which could mislead slightly.

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?

Given a destructive full-field write against a very deep nested schema and no output schema, the description covers scope and entity purpose but leaves the semantics of replacement (does omitting a leaderboard from Definitions delete it? do presets merge or override?) and any permission/validation expectations unstated.

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 coverage is 100% and the nested LeaderboardDefinition is heavily documented, so the baseline is 3. The description earns one more by summarizing the semantic axes of the `value` payload (name, score type, cadence, rewards, eligibility) before the agent dives into the deep schema.

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 names a specific verb and resource ('save_leaderboard') and states the exact write scope: only the 'Leaderboard' field of TitlePublicConfigurationModel, with all other v1/v2 fields untouched. The enumeration of what a leaderboard actually is (ranking metric, reset cadence, rank rewards, eligibility) makes the tool unmistakable against get_leaderboard and the other save_* siblings.

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?

'Use for pure player-vs-player ranking. For collaborative team goals use CoopEvent' gives an explicit exclusion and a named alternative. It does not spell out the read/write contrast with get_leaderboard, but the write/partial-save framing already makes that inference cheap.

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