Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Early Access settings

save_early_access
Destructive

PARTIAL SAVE: writes ONLY the 'EarlyAccess' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. EarlyAccess - early token purchase: while the game's token is on its bonding curve and its early phase is open, only players holding a pass may buy it. The phase itself (duration up to 7 days, total cap, no-sell) is fixed when the token is launched, allowed by the platform per title or publisher, and frozen on chain - this section cannot change it. Enabled is the master switch (default OFF). Tiers: each has TierID, MaxQuote (how much of the chain's quote token in wei the player's wallet may spend in the phase in total), NotBeforeUtc (the wave; empty = at once) and Conditions, ALL of which must hold: QuestCompleted {QuestID} (hours played, logins, kills and any metric are quests), ItemOwned {ItemID, MinAmount default 1, MinLevel}, LeaderboardRank {LeaderboardID, MaxRank}, CloudCodeGrant {GrantID, given by a script with server.GrantEarlyAccess}, Segment {Gate}. Empty Conditions = any player with a verified wallet. A player gets the best tier (higher MaxQuote, then the earlier wave); OR = several tiers. The player requests the pass himself (EarlyAccess.GetPass); it is personal, bound to one wallet, never published.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title_id": "<title_id>",
      "value": "<value>"
    },
    "name": "save_early_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesEarly token purchase: while the game's token is on its bonding curve and its early phase is open, only players holding a pass may buy it. Whether the token has a phase, how long it lasts and whether selling is blocked were fixed when the token was launched and are frozen on chain. This section only says WHO the engine signs a pass for: Tiers, each with its own purchase cap and wave. A player gets the best tier whose conditions all hold. The pass is personal and requested by the player; nothing is published.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare a non-read-only, destructive mutation, and the description adds important scope details: only the EarlyAccess field is written while other v1/v2 fields remain untouched. It also explains that phase rules are frozen on chain and cannot be changed here, though it does not explicitly state whether existing tiers are replaced wholesale.

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 front-loaded 'PARTIAL SAVE' statement is effective, but the description is a long dense paragraph with extensive domain exposition. Several sentences repeat schema content or provide contextual detail that is useful but not strictly necessary for invoking the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter but deeply nested save operation, the description supplies the missing operational context: what is saved, what is not changed, how tiers and conditions behave, and that passes are player-requested and personal. Combined with the rich schema and annotations, an agent has enough information to call it correctly.

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%, so the nested schema already documents Enabled, Tiers, TierID, MaxQuote, NotBeforeUtc, and Conditions in detail. The description reinforces and synthesizes that meaning, especially best-tier selection and OR-via-multiple-tiers behavior, but much of it repeats what the schema already says.

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 resource: 'PARTIAL SAVE' writes only the 'EarlyAccess' field of TitlePublicConfigurationModel. It clearly distinguishes this write operation from reading early-access settings and from changing the on-chain phase configuration.

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 gives clear context for when this tool applies: it controls who receives an early-access pass, not the token phase, duration, cap, or no-sell rules. It does not explicitly name get_early_access or another sibling as the read alternative, so routing guidance is strong but not fully explicit.

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