Skip to main content
Glama

Read game data and docs

game_data
Read-onlyIdempotent

Read the game's data and docs, the same as the agentickingdoms://data, ://docs and ://text resources: with no name, the index plus the formulas (research, training, healing, speed-up prices); a data set (alliance_research, alliance_store, black_market, buildings, city_plots, combat, dragons, economy, events, gear, hero_skills, heroes, leagues, limited_time_sales, meta, packs, quests, research, titles, troops, tutorial, vip, war_machines); a doc (agent-payments, ai-player-guide, game-mechanics, how-to-play, mcp-server, player-actions, protocol); or text-en (display names and tutorial text). player-actions has every command's payload shape.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoa data set (e.g. research, troops, packs), a doc (e.g. player-actions), or text-en; leave empty for the index and the formulas
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, and an output schema covers the return shape, so the bar is lower. The description adds real behavior beyond that: the empty-name default returns the index plus pricing formulas, and the token is only needed as a retry after a not_logged_in response, which is non-obvious recovery guidance.

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?

Front-loaded with the core action and organized into three semicolon-delimited cases (index, data set, doc/text), with the payload-shape hint saved for last. The long name enumeration is dense but each entry is a valid value an agent needs, so almost nothing is waste.

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 read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: the complete value vocabulary, the empty-name behavior, the auth-retry rule, and a pointer to where command payloads are documented. No material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description still adds meaning the schema only gestures at: the full closed list of valid data set and doc names, and the semantics of leaving name empty. The token semantics (retry-only after login) are also restated helpfully rather than merely duplicated.

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 ("Read the game's data and docs") and then enumerates exactly which data sets, docs, and text bundles are readable, plus the empty-name index/formulas case. Nothing in the sibling list (all account, auth, purchase, or send_command tools) overlaps, so the agent can route here for reference material 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?

Gives clear context for choosing a value: no name for index+formulas, a data set name for game numbers, a doc name for prose, or text-en for display strings, and points at player-actions for command payload shapes. It does not explicitly say when not to use it or name an alternative tool, but there is no sibling that competes for this job.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources