Skip to main content
Glama

Add earlier plays to my account

claim_plays

Attaches plays made earlier without an account to the signed-in player's Plot Speaks account, so they appear in their history (with how each ended) and in the "not played yet" filter, and marks the trivia clues already heard in those games. Returns a sentence naming the titles added and how many could not be added (id not found, or already on another account). Without a signed-in account it returns an error saying so. Changes the account's history; plays on another account are left alone. 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": {
      "play_ids": "<play_ids>"
    },
    "name": "claim_plays"
  }
}

Input Schema

NameRequiredDescriptionDefault
play_idsYes1 to 50 play ids, as returned by start_story, e.g. ["3f2b8c1e-9d4a-4e7b-a1c2-5b6d7e8f9a0b"]; ids of plays made in this conversation without an account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / play_ids / description
      Previous value: -"Play ids from earlier in this conversation (start_story returned them)"New value: +"1 to 50 play ids, as returned by start_story, e.g. [\"3f2b8c1e-9d4a-4e7b-a1c2-5b6d7e8f9a0b\"]; ids of plays made in this conversation without an account"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations by describing what gets mutated (history entries with outcomes, the 'not played yet' filter, and already-heard trivia clues), what is deliberately left alone (plays on another account), the return value shape, and the failure modes (id not found, already claimed elsewhere, no signed-in account). It adds a communication constraint (never say 'let me check') that no structured field carries. It does not say what happens if the same play id is claimed twice, leaving the non-idempotent hint unexplained.

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 core effect and side effects are front-loaded and earn their place. However, the closing instruction pads out with four near-duplicate forbidden phrases ('let me check', 'let me check on that', 'one moment', 'hang on'), which inflates length without adding precision.

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 single-parameter mutation with no output schema, the description covers outcome, side effects, exclusions, return format, and error behavior. The only real gap is repeat-claim behavior, which the idempotentHint=false annotation hints at but the description never addresses.

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% and the single parameter already documents the 1-50 id array, its format, and its provenance from start_story. The description's mention of 'plays made earlier without an account' corroborates the parameter's meaning but adds no new syntax or constraint beyond the schema.

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?

States a specific verb and resource: 'Attaches plays made earlier without an account to the signed-in player's Plot Speaks account.' It also makes the scope distinction explicit ('plays made earlier without an account'), which separates it from the story-play siblings like start_story or my_history.

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

Usage Guidelines4/5

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

Gives a clear triggering condition: plays made in this conversation without an account, whose ids came from start_story. It does not name an alternative tool or an explicit when-not, so it stops short of a 5, but the usage context is unambiguous.

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