Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Get Early Access settings

get_early_access
Read-only

GET ONLY the 'EarlyAccess' field of TitlePublicConfigurationModel. 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>"
    },
    "name": "get_early_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
title_idYesTitleID, для которого читаются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious domain behavior: Enabled defaults to OFF, the phase parameters are frozen on chain and cannot be changed via this section, tier selection picks the best tier (higher MaxQuote, then earlier wave), and passes are personal and never published.

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?

Scoring corrected to reflect that the single title-scoped question is answered up front and every subsequent clause explains a field the caller cannot otherwise know, given that no output schema exists.

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?

With no output schema, the description has to carry the shape of the returned EarlyAccess object, and it does — master switch, tier fields, condition types, and tier-resolution rules. It omits error behavior and whether an unconfigured title returns an empty object.

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?

Only one parameter with 100% schema description coverage, so the schema already documents title_id. The description adds no format, scope, or failure-mode detail about title_id itself, which is the baseline-3 case.

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 and resource with explicit narrowing: "GET ONLY the 'EarlyAccess' field of TitlePublicConfigurationModel." This distinguishes it from save_early_access (the write counterpart) and from broader config readers without needing to open any schema.

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 word "ONLY" implies that other configuration fields live elsewhere (e.g., get_title_data), but no sibling is named and no explicit when-to-use/when-not-to-use rule is given. Usage is inferable from scope rather than 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