Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Blockchain settings

save_blockchain
Destructive

PARTIAL SAVE: writes ONLY the 'Blockchain' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. On-chain integration config — chain selectors, smart contract addresses, RPC overrides, gas policy, supported networks for Crypto currencies. Built largely from Currency.CryptoCurrencies[].Networks; this is the title-level companion config.

Input Schema

NameRequiredDescriptionDefault
valueYesV2 definition of the title's blockchain integration. Contains only public data safe for clients (chain IDs, contracts, feature switches, safety policies). Private data lives in TitlePrivateConfiguration.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / definitions / PlayerWithdrawalsSwitch
      Added value: +{
+  "description": "Player withdrawal switch of the title. Read-only for config writes; changed only by the owner's consent action.",
+  "properties": {
+    "ChangedAt": {
+      "description": "When the switch was last changed (UTC).",
+      "format": "date-time",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "ChangedBy": {
+      "description": "Publisher user who last changed the switch.",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "ConsentID": {
+      "description": "ID of the consent journal record of the last change.",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "Enabled": {
+      "description": "Whether players may withdraw crypto from this title.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / value / properties / PlayerWithdrawals
      Added value: +{
+  "description": "Read-only. Whether players of this title may withdraw crypto out of the game. Absent = off. Only the title owner can switch it, in the dashboard, after accepting the legal responsibility terms; config writes (dashboard, MCP, DEV/PROD transfer) never change it. Works only while the platform also allows player withdrawals.",
+  "oneOf": [
+    {
+      "type": "null"
+    },
+    {
+      "$ref": "#/definitions/PlayerWithdrawalsSwitch"
+    }
+  ]
+}
  2. Changed1 schema field changed
    • addedInput schema / definitions / BlockchainWalletLoginPolicy / properties / ShowOnLoginScreen
      Added value: +{
+  "description": "Show the 'Sign in with wallet' button on the game's sign-in screen even when the title's login mode is Open. By default the button appears only in a token-gated login mode. Takes effect only together with Enabled.",
+  "type": "boolean"
+}
  3. 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, so the safety profile is known. The description adds meaningful non-schema behavior: the write is scoped to a single field, leaving all other v1/v2 fields untouched, and clarifies this config is derived from currency network definitions. It omits any auth/ownership requirements or side effects of saving, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the critical 'PARTIAL SAVE' qualifier, followed by scope and data-origin context. No filler, and the most decision-relevant fact comes first.

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 mutation with a deep nested schema and no output schema, the description adequately frames scope and data provenance. It could add ownership/permission requirements or whether a save requires a subsequent on-chain action, but the essential call-time context is present.

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% with extensively documented nested properties, so the schema carries the parameter burden. The description adds only one relational hint (value is largely built from Currency.CryptoCurrencies[].Networks) and does not explain title_id or value structure further, so it sits at the baseline.

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?

Opens with a specific verb and scope: 'PARTIAL SAVE: writes ONLY the Blockchain field of TitlePublicConfigurationModel'. It names the exact resource written and immediately contrasts with the whole-title save sibling, so an agent can distinguish it from save_title_data/save_currency without opening a 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 states when this tool is appropriate (partial write of only the Blockchain field; other fields stay untouched) and warns that related data lives in Currency.CryptoCurrencies[].Networks. It does not explicitly name the alternative tool (e.g. save_title_data) or exclusion cases, which keeps it from a 5.

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