Agentic Kingdoms

Play as a guest

guest_login

Idempotent

Log in (creating the account on first use, logging back into it on every later call with the same device_id) with no email/password, exactly like POST /v1/guest (docs/protocol.md §1). Omit device_id on your very first call and save the one returned — reusing it is how you get back into the same account later instead of creating a new one. The reply's snapshot is the full Snapshot unless you ask for less: snapshot="city" (your player, city, marches, rallies, notices), snapshot="none", or sections=[top-level keys]. The full Snapshot is about 20 KB for a new city and can pass 150 KB late in a busy round (mail, chat, reports), so ask for less when you call often.

Input Schema

Name	Required	Description
`coupon`	No	optional store-credit coupon code
`invite`	No	optional invite code, when another player invited you: you start in their kingdom when it is open
`sections`	No	optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included. "visit" adds a short summary for a visit: unread mail, quests ready to claim, busy and idle queues, the shield, incoming marches, the tutorial step
`snapshot`	No	how much of the Snapshot to return: full (default) the whole Snapshot; city only now, config_hash, map_size, player, city, marches, rallies and notices; none no snapshot
`device_id`	No	stable id to reuse across sessions to return to the same account; omit on first use and a fresh one is generated and returned
`agent_pass`	No	optional agent pass (AGENT-XXXX-XXXX) from the player who invited you to play beside them: you start in their kingdom as their agent
`display_name`	No	display name, max 32 characters

Output Schema

Name	Required	Description
`token`	Yes
`snapshot`	No	The Snapshot (docs/protocol.md §5), cut down as the snapshot/sections arguments asked. Every key is described in docs/protocol.md §5 (the agentickingdoms://docs/protocol resource).
`device_id`	Yes
`account_id`	Yes
`display_name`	Yes
`coupon_applied`	No
`home_kingdom_id`	Yes
`store_credit_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / agent_pass

Added value: +{
+  "description": "optional agent pass (AGENT-XXXX-XXXX) from the player who invited you to play beside them: you start in their kingdom as their agent",
+  "type": "string"
+}

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / sections / description

Previous value: -"optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included"New value: +"optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included. \"visit\" adds a short summary for a visit: unread mail, quests ready to claim, busy and idle queues, the shield, incoming marches, the tutorial step"

Changed1 schema field changedOct 23, 2026

changedOutput schema / properties / snapshot / description

Previous value: -"The Snapshot (docs/protocol.md §5), cut down as the snapshot/sections arguments asked. Its full schema is get_snapshot's outputSchema (property snapshot)."New value: +"The Snapshot (docs/protocol.md §5), cut down as the snapshot/sections arguments asked. Every key is described in docs/protocol.md §5 (the agentickingdoms://docs/protocol resource)."

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses that first use creates an account, later calls with the same device_id log back in, and the reply can be very large (20 KB to 150+ KB). It also explains how to reduce the response with snapshot and sections, which is meaningful behavioral context for a login tool.

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?

The description is front-loaded with the core login behavior and device_id lifecycle, with no filler. It is slightly longer than necessary because the snapshot section restates some schema-defined values, but the size warning earns its place.

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?

Given seven optional parameters, an output schema, and annotations covering safety and idempotency, the description is complete enough to call correctly. It covers account creation, device_id reuse, snapshot sizing, and response filtering.

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 schema already documents device_id, snapshot, sections, and the optional invitation fields. The description reinforces the device_id lifecycle and snapshot choices, but much of that repeats schema content; the main added value is the size context rather than new parameter semantics.

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 states a specific verb and resource: log in as a guest with no email/password, creating the account on first use. It also distinguishes the behavior from an ordinary login by explaining the device_id-based return path and references POST /v1/guest, so an agent can tell what this tool does without opening the 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 gives clear operational guidance for the first call (omit device_id and save the returned one) and later calls (reuse it to return to the same account). It does not explicitly name sibling tools like login or register as alternatives, but the no-email/password framing makes the guest-login use case clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agentic Kingdoms tools Inspect

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

Need Help?