Skip to main content
Glama

Golemreach

by io.github.aniripsaretro-max
OverviewDiscussionsAdmin

Lantern Guild expeditions and trophies

golemreach_guild

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.

Choose a short hunt, survey or named champion challenge after collecting your starter kit. Board shows locks, first-clear trophies, rewards and earned titles. Accept one expedition; your observation gives its route and next action. Survey at a marker, challenge near its hunting ground, claim from sanctuary with supplies or extra gold. Abandon freely. Champion dangerZones show fixed strike tiles and time to dodge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
rewardNo
operationNoboard
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.
expeditionIdNo

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. Added

TDQS

A3.8/5.0
Behavior4/5

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

Since there are no annotations, the description carries the behavioral burden. It meaningfully discloses that sessionId grants character control, that abandoning is free, and that champion dangerZones show fixed strike tiles and dodge timing. It stops short of describing exact effects of every operation, but it is substantially transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is not overly long, but the first paragraph repeats the sessionId guidance that already appears in the sessionId parameter description. The second paragraph is dense and useful, so the duplication keeps this at average rather than high.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool has five parameters, an enum-heavy operation list, and no output schema, so the description needs to fill many gaps. It does not explain where expeditionId comes from, what response each operation returns, or how the 'title' operation works. The overall game loop is described, but call-critical details are missing.

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 coverage is only 20%, so the description must compensate. It explains reward via 'supplies or extra gold' and maps many operation values into the workflow. However, it never explains the 'title' parameter or when 'expeditionId' is required, leaving two of five parameters underspecified.

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 title and description clearly identify the resource: Lantern Guild expeditions and trophies. It names distinct operations like board, accept, survey, challenge, claim, abandon, and title, which separates it from sibling tools such as golemreach_attack or golemreach_trade.

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 provides a start-to-finish workflow: get a sessionId via golemreach_connect, collect the starter kit, pick an expedition, then survey, challenge, claim, or abandon. It does not explicitly say when not to use this tool or point to alternatives for non-guild actions, but the context is clear enough for an agent to follow.

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