Skip to main content
Glama

What I've played

my_history
Read-onlyIdempotent

Returns what a signed-in Plot Speaks player has played, newest first, with how each ended. Without an account it says how to get one. 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

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to list (default 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond that: newest-first ordering, the 'how each ended' payload, the unauthenticated fallback behavior, and a user-facing silence constraint on how the call is narrated.

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?

Front-loaded with the purpose in one sentence, then the fallback behavior, then the silence rule. The forbidden-phrase list is somewhat repetitive (it restates the 'let me check' idea twice) but each clause maps to a distinct output or narration rule.

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 one-optional-param read tool with no output schema, the description covers the return content (chronological plays with outcomes), the empty/unauthenticated case, and the narration constraint. Nothing essential to calling it correctly is missing, though it does not mention whether results beyond 50 are paginated.

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 single limit parameter (1-50, default 15) is already fully documented in structured data. The description adds no extra meaning about the limit, so the baseline of 3 applies.

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 (returns what a player has played) plus scope details: signed-in only, newest first, with how each ended. This is enough to separate it from adjacent siblings like submission_status or claim_plays without opening another schema.

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 gives invocation guidance ('call it silently') and covers the unauthenticated case, but it never states when an agent should reach for this versus a sibling such as submission_status or world_recall. Usage is implied by the signed-in player framing rather than explicitly bounded.

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