Skip to main content
Glama

get_changes

Retrieve only map cells changed since a given version to efficiently react to other players. Includes server reachability status to avoid actions when down.

Instructions

Get only the cells that changed since a given version — react to other players without re-reading the whole map. Workflow: take "version" from a previous map response, remember it, and pass it back here next time; the response carries a new "version" to use on the following call. Omit sinceVersion (or pass 0) to get everything. The response also carries "server": { reachable }. reachable=false means the game server is unreachable right now (the last HTTP call to the API failed or returned non-JSON), so any action (build/reveal/transport/trade) will fail too — do not hammer it with retries. Keep polling get_changes instead: the client keeps probing and reconnecting in the background, and once "server".reachable flips back to true the server is up and you can act again (after an outage, call once with sinceVersion 0 to be sure you have the full current picture).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceVersionNoThe "version" (epoch ms) from a previous map response. Omit or 0 to return every cell.
Behavior5/5

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

No annotations exist, so description fully carries burden. Discloses response fields (version, server.reachable) and explains behavior during outages, including client-side reconnection. No contradictions.

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?

Description is detailed but well-structured: starts with purpose, then workflow, then edge cases. Could be slightly shortened but every sentence adds value.

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?

No output schema, but description explains response structure (version, server.reachable) and handles recovery from outages. Complete for a polling tool with no missing context.

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

Parameters5/5

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

Schema has 100% coverage for sinceVersion parameter. Description adds crucial context: how to use previous version, omit/0 behavior, and the returned version field. Exceeds schema detail.

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?

Clearly states it gets changed cells since a version, differentiating from get_map which returns everything. The workflow explanation reinforces the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (react to others) and provides detailed guidance on version parameter, server unreachable behavior, and polling strategy. Includes what to avoid (retries).

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