Skip to main content
Glama

get_map

Retrieve a current snapshot of the game world map, with optional scopes for your cells, surrounding hexes, specific cells, or a full overview. Includes neighbor connections and resource holdings.

Instructions

Read the live game world. The map is loaded at startup and kept current in the background; this returns a snapshot of it on demand (you only see updates when you call a tool). The map is public — you can see every player. Resources live on cells. Always returns a "summary" (counts + freshness) and, when your wallet is known, a "resourceIndex" (resourceId → your cells holding it, with location). Cells come back as a graph: each carries axial x/y and "neighbors" (the 6 adjacent hexes, each owned/other/empty). Scopes: "mine" (your cells), "around" (cells within a hex radius — scout a region), "cells" (specific tokenIds), "all" (everything), "summary" (no cells). Default: "mine", else "summary". Note units: version/updated are epoch ms, serverTime/startAt are unix seconds, amounts are decimal strings. Also carries "server": { reachable } — false means the game server is unreachable right now and actions will fail; retry once it is true again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNomine | around | cells | all | summary. Omit to default to "mine" (or "summary" if no wallet).
tokenIdsNoRequired for scope="cells": the cell tokenIds to return.
centerXNoAxial x of the centre for scope="around".
centerYNoAxial y of the centre for scope="around".
radiusNoHex radius for scope="around" (default 2, max 10).
Behavior5/5

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

With no annotations, the description fully bears the burden. It discloses that the map is a snapshot updated only on call, explains the return structure (summary, resourceIndex, cells as graph, server reachability), and notes units of measure.

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 somewhat lengthy but well-structured: purpose first, then behavior, scopes, notes on units, and server field. Every paragraph adds necessary detail, though some could be tightened.

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 no output schema, the description fully explains the return values (summary, resourceIndex, cells graph, server field) and covers all params. With siblings like get_cell and get_changes, this provides sufficient context for selection and invocation.

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?

The schema already describes all parameters (100% coverage), but the description adds context beyond the schema by explaining defaults, scope behavior, and the exact meaning of 'around' parameters. This raises the value above baseline 3.

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 clearly states 'Read the live game world' as a specific verb-resource combination, and differentiates from siblings like get_cell by describing the map as a snapshot with graph structure and multiple scopes.

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?

The description explains each scope ('mine', 'around', 'cells', 'all', 'summary') with defaults and the conditions for using 'summary' when no wallet is known. It also covers server reachability for actions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sodiqit/cpu-game-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server