Whiteout Survival State Transfer tracker: phase dates, active status, remaining pass chances.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.3/5 across 1 of 1 tools scored.
With only one tool, there is no ambiguity between tools. The single tool has a clearly defined purpose.
The single tool name follows a clear descriptive verb_noun pattern (get_upcoming_state_transfer), which is consistent within the set.
One tool is borderline: it may be appropriate for a very narrow domain, but generally a single tool feels thin for a server.
The tool provides comprehensive information for the stated domain of state transfer tracking, including all relevant dates, active status, and shop chances.
get_upcoming_state_transferAInspectReturns the current or next upcoming State Transfer event for Whiteout Survival: dates for the three transfer phases (power cap setup, invitations, transfer passes), whether the transfer is currently active, and how many weekly chances remain to buy a Transfer Pass from the Alliance Shop before the transfer date. Dates are in UTC, formatted as "Year/Month/Day" (e.g. "2026/07/19"). transferDate is a "Month Year" label identifying the transfer window (e.g. "July 2026").
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the output in detail: dates in specific format, timezone (UTC), what each field represents, and the scope (current/next upcoming). It does not mention side effects or auth needs, but for a read-only getter, this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise yet comprehensive. Every sentence adds necessary detail about the output fields, format, and timezone. It is front-loaded with the core purpose and uses efficient, direct language without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters and no output schema, the description fully compensates by listing all return values, their meanings, and format details. It is complete for an agent to understand exactly what the tool returns and how to interpret the data.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so the input schema is empty. The description does not need to explain parameters. It adds value by describing the output that corresponds to the implicit no-parameter call. Baseline 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the upcoming State Transfer event for a specific game, listing all returned elements (dates, phases, active status, weekly chances). It uses a specific verb ('Returns') and resource ('State Transfer event'), and the description is unique enough to distinguish it from any potential siblings (none provided).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives, nor are there any siblings or exclusion conditions mentioned. However, the purpose is clear and usage is implied for retrieving transfer event details. It lacks guidance on when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!