Skip to main content
Glama

Golemreach

by io.github.aniripsaretro-max
OverviewDiscussionsAdmin

Talk to an NPC

golemreach_talk

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.

Say something to a non-player character. NPCs take free-form English — they are the one part of this world built for language rather than around it — so "hello", "what do you sell?", "where can I hunt?" and "do you have anything for a level 3 knight" all work.

THIS IS NOT FLAVOUR. Talking is how you find out where anything is and how you get work, and there is no other way to do either. The two topics that matter:

  • ASK "where can I hunt?" (or say "hunt", "monsters", "danger") and ANY npc names somewhere suited to your level and puts it in your knowledge as a lead. A lead is a name and a direction, never coordinates — go and find the place, and arriving turns it into a real destination. Ask again after you have found it and they will point you somewhere new.

  • ASK about "task" (or "quest", "job", "work") and they offer you one. ASKING IS ACCEPTING — there is no separate yes. Kills count on their own from that moment; fetch objectives just check your backpack. Come back to THE SAME npc and ask about "task" again to hand it in; they will tell you what is still outstanding and its exact counter if you are early. Check progress any time with golemreach_where.

Ask about "trade" to make a merchant list its stock with prices; then buy with golemreach_trade. NPCs never dead-end: if one cannot understand you it tells you what it does know about.

Get npcId from the CREATURES list in a look (ids like "n3"), or use the content id from golemreach_where (ids like "general_store"). Both are accepted.

RETURNS: what the NPC said, plus their stock list when the topic was trade.

COMMON FAILURE: "out_of_range" — you must be within 3 tiles to be heard. Walk closer with golemreach_move first; the npc's exact tile is in the CREATURES list of a look.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesWhat you say. Plain English.
npcIdYesThe NPC, either a live creature id like "n3" or a content id like "general_store".
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.

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.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it succeeds. It discloses key behavioral details: asking about task is accepting it, kills count automatically, hand-in must be with the same NPC, out_of_range means you are beyond 3 tiles, leads are name/direction only, and the response includes stock on trade topics.

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

Conciseness5/5

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

The description is long but dense and well-organized, with each paragraph covering a distinct concern: sessionId handling, core behavior, key topics, return values, and failure recovery. The sessionId warning is front-loaded because it is required for every call, and no sentences are wasted.

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 the tool's complexity and the absence of an output schema, the description is remarkably complete. It covers inputs, ID resolution, behavior, return values, common failure modes, range requirements, and the exact mechanics of task acceptance and hand-in. An agent has enough information to use this tool correctly without further investigation.

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 covers all three parameters, giving a baseline of 3. The description goes beyond the schema by explaining where npcId values come from ('n3' vs 'general_store'), showing that text is free-form English, and adding example phrasings. This is substantial supplemental meaning but not exhaustive for every parameter.

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 names a specific verb and resource: 'Say something to a non-player character,' and clearly explains the broader purpose of talking, such as discovering locations and getting work. It also distinguishes itself from related tools by pointing to golemreach_trade for buying and golemreach_where for progress checks.

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?

Usage guidance is explicit and actionable: call golemreach_connect first if you lack a sessionId, use golemreach_move when out_of_range, use golemreach_trade for buying, and use golemreach_where to check progress. It also states that talking is the only way to find locations and get work, making the decision to use this tool clear.

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