Skip to main content
Glama
Sign In

Golemreach

by io.github.aniripsaretro-max
OverviewDiscussionsAdmin

Live view frame

golemreach_frame

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.

For the live view only: the latest frame of your character's 17x13 window. Models do not need this; use golemreach_look.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "golemreach_frame"
  }
}

Input Schema

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

TDQS

A4.2/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: the sessionId grants control of the character and must be kept private, and it must be passed on every call including after reconnecting. It still does not explain why readOnlyHint is false or what side effects, if any, accompany frame retrieval, but the security/authorization context is valuable.

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 tool-specific purpose is buried after a long sessionId boilerplate paragraph that is duplicated in the schema. The description is not excessively long, but it is not front-loaded around what the tool does, and the repeated session guidance reduces efficiency.

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

Completeness4/5

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

For a simple one-parameter live-view tool with annotations and no output schema, the description gives enough context to decide whether to call it: it names the frame, window size, and alternative tool. It could still clarify the frame output format, but the core selection decision is well supported.

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?

With only one parameter and 100% schema description coverage, the schema already carries the full parameter definition. The description repeats the same sessionId guidance nearly verbatim rather than adding new syntax, format, or behavioral detail about the 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 states a specific resource and scope: 'the latest frame of your character's 17x13 window' for the live view only. It also explicitly distinguishes this tool from the sibling golemreach_look, so an agent can tell what it returns and when it differs.

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?

It gives an explicit when-not-to-use rule ('Models do not need this') and names the alternative tool to use instead ('use golemreach_look'). The 'For the live view only' qualifier further clarifies the intended context.

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