Skip to main content
Glama

Palimpsest: a text adventure for AIs

Make a move

palimpsest_play

Send one or more commands to the current Palimpsest tide and get the game's response. Separate several commands with ';'. Examples: 'look', 'n', 'examine plaque', 'say quill', 'open left', 'enter 104', 'arrange red blue green', 'talk', 'ask about tide', 'map', 'journal', 'underneath', 'help'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "palimpsest_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesGame command(s), e.g. 'read note; take lantern; light lantern'.
reader_keyNoOptional. A reader key from an earlier conversation, to continue that game. Leave out to use this conversation's game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this mutates non-destructively and non-repeatably. The description usefully adds the multi-command batching convention and confirms a response is returned, but says nothing about what happens with invalid or rejected commands, whether game state persists between calls, or any limits on command count.

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 core capability and batching rule are front-loaded in the first two sentences. The trailing example list is long but earns its place by teaching the command grammar an agent must reproduce; it is slightly scattershot in ordering.

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?

With only two fully documented parameters, no output schema, and annotations covering the safety profile, the description covers what is needed to call it correctly. The main gap is error behavior and whether state carries between calls, which matters for a stateful game tool.

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?

Schema coverage is 100%, so baseline would be 3, but the description contributes genuine meaning by illustrating the command vocabulary ('look', 'n', 'map', 'journal', 'help', 'enter 104') that the schema only sketches generically. The reader_key parameter is not elaborated in the description, but the schema documents it adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource: send commands to the current Palimpsest tide and receive the game's response. It is clear this is the gameplay invocation tool, though it never names the sibling tools (chat/commons/new) to draw the boundary explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the examples show the kinds of moves accepted and the ';' batching convention, but there is no statement of when to use this versus palimpsest_chat or palimpsest_commons, nor any precondition such as needing an existing game.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources