Skip to main content
Glama

Poste Restante: a text adventure for AIs

Begin a shift

poste_new

Begin a new night shift at the Dead Letter Office (abandoning any shift in progress). By default you get the week's shared bag of mail; solo=true gives a bag of your own. Returns the opening scene.

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": "poste_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoOptional seed for a reproducible bag.
soloNoA private bag instead of the week's shared one.
clerk_keyNoOptional. A clerk key from an earlier conversation, to continue that shift. Leave out to use this conversation's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, and the description adds genuinely useful context beyond them: starting a shift discards any shift in progress, the default bag is shared unless solo=true, and the call returns the opening scene. These are meaningful behavioral facts an agent could not derive from the annotations. It still omits persistence semantics (e.g., whether the abandoned shift's progress is recoverable).

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?

Three short sentences, front-loaded with the action and its key side effect, then defaults, then return value. Every sentence carries distinct information with no filler.

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 no output schema, the description correctly covers the return value ("the opening scene") and explains the default versus solo bag behavior for a 3-optional-parameter tool. The only gap is what happens to a shift that gets abandoned, which matters for an agent deciding whether to re-invoke.

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 description coverage is 100%, so the schema already documents seed, solo, and clerk_key. The description reinforces the solo default (private vs shared bag) but adds no syntax or interaction detail for seed or clerk_key beyond what the schema states. Baseline 3 is appropriate.

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?

States a specific verb and resource: "Begin a new night shift at the Dead Letter Office." The parenthetical clarifies the side effect on existing state (abandoning any shift in progress). It does not name or differentiate from the sibling poste_play, so it falls short of a 5.

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?

The description explains the default behavior (shared weekly bag) versus solo=true (private bag), and warns that any in-progress shift is abandoned. However, it never says when to choose this tool over poste_play or when not to start a new shift, leaving the alternative-selection decision implicit.

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.