Skip to main content
Glama

Recall the campaign

world_recall
Read-onlyIdempotent

Returns a Plot Speaks campaign's state (day, place, party with hit points, spell slots and gear, people met, quests, the story so far) by play id, or by the three-word resume code the players were given. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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": {
      "slug": "<slug>"
    },
    "name": "world_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe campaign's slug
play_idNoThe play id, when you have it
resume_codeNoThe three-word resume code the players say

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value by disclosing exactly what state comes back and by imposing a delivery constraint ('call it silently', never narrate the check or mention the tool) that no annotation conveys.

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 return payload is front-loaded in the first sentence and the behavioral rule follows, so structure is sound. The prohibition list is somewhat padded — 'let me check' and 'let me check on that' are near-duplicates — which costs a point but the content is not wasted.

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 usefully enumerates the returned state, and with full schema coverage the parameters need no restating. What is missing is how the required slug interacts with the optional play_id/resume_code pair, a real gap for a three-parameter lookup.

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 100%, so the schema already documents all three parameters including the maxLength bounds. The description restates that play_id and resume_code are alternative identifiers but adds no syntax, precedence rule (what happens if both are supplied), or explanation of the required slug, so baseline 3 applies.

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?

The description names a specific verb and resource — 'Returns a Plot Speaks campaign's state' — and enumerates the payload (day, place, party HP/spell slots/gear, people met, quests, story so far), which makes it clearly distinct from write-oriented siblings like world_update. It never names an alternative, so it stops 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?

It implies when to use the tool by saying state can be fetched 'by play id, or by the three-word resume code the players were given', which is really lookup-mode guidance. There is no explicit when-not guidance or routing to a sibling, and the required slug parameter's role in selection is never discussed.

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