Skip to main content
Glama

Golemreach

by io.github.aniripsaretro-max
OverviewDiscussionsAdmin

Enter Golemreach

golemreach_connect

Pass the sessionId returned by golemreach_connect with EVERY tool call, including after reconnecting. Keep it private: it grants control of your character. If you have no sessionId yet, call golemreach_connect once.

Join the game. This is always your first call. It registers an account, creates a character and walks it into the world in one step, then returns your first look at the world.

Call it again later only if you were disconnected; it remembers your token and character between runs, so a second call resumes the same character rather than making a new one (pass fresh:true if you really want a new account).

RETURNS: your character name, level and vocation, plus the standard world view — status line, ASCII map, creatures in sight, and any hints the server has for you.

COMMON FAILURE: "Could not reach the Golemreach server" means the game server is not running. Start it with node packages/server/dist/main.js --port 7171, or pass serverUrl if it listens elsewhere. The other one is a character name collision — names are unique across the whole server, so pass a different characterName.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freshNoIgnore any remembered account and register a brand new one.
tokenNoAn existing account token, if you already have one.
vocationNoClass for a NEW character; ignored when resuming. knight = most health and melee damage, no real magic, the easy start. paladin = ranged, self-sufficient. sorcerer = huge damage, dies instantly. druid = healing and ice. Default knight, which is the forgiving choice for a first character.
agentNameNoLabel for your account and for spectators watching the world.
serverUrlNoBase URL of the game server, e.g. "http://localhost:7171". Defaults to GOLEMREACH_URL or http://localhost:7171.
sessionIdNoPass the sessionId returned by golemreach_connect with EVERY tool call, including after reconnecting. Keep it private: it grants control of your character. If you have no sessionId yet, call golemreach_connect once.
characterIdNoAn existing character id on that account, e.g. "ch4".
characterNameNoName for a new character. Must be unique server-wide. Omit to get a generated one, or to resume an existing character.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Pass the sessionId returned by golemreach_connect with EVERY tool call, including after reconnecting. Keep it private: it grants control of your character. If you have no sessionId yet, call golemreach_connect once.",
+  "pattern": "^gs_[A-Za-z0-9_-]{43}$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: it discloses side effects (account registration, character creation), persistence semantics (token and character are remembered between runs), security implications (sessionId grants character control), and common failure modes with remedies.

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 fairly long but nearly every sentence is load-bearing, and it is well-structured with clear sections for returns and common failures. The most critical rule about sessionId is front-loaded. Minor redundancy between the description and the schema's sessionId text keeps it from a 5.

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?

There is no output schema and no annotations, yet the description covers the mandatory first-call behavior, resumption semantics, return contents, parameter hints, and failure recovery. An agent has enough context to call this tool correctly and know what to expect.

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 input schema already covers 100% of parameters with helpful descriptions, so the baseline is 3. The description adds meaningful operational context for fresh, characterName uniqueness/collisions, token persistence, and the need to pass sessionId with every call, going slightly beyond the schema.

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 the tool's exact purpose: 'Join the game', 'registers an account, creates a character and walks it into the world in one step'. It also establishes itself as the mandatory entry point: 'This is always your first call', which separates it from the gameplay-action sibling tools.

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?

The description gives explicit usage conditions: call it first, call it again only after disconnection, and pass fresh:true only when a brand new account is wanted. It also includes a concrete recovery path for the common server-unreachable failure, telling the agent to start the server or pass serverUrl.

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

All Golemreach toolsInspect
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