Skip to main content
Glama

Plot Speaks

by com.plotspeaks
OverviewDiscussionsAdmin

List stories

list_stories
Read-onlyIdempotent

Lists the Plot Speaks stories and games that can be played by voice, three at a time with a one-line pitch each; the page argument gives the next three. Narrow it by a collection (Murder Mysteries, Greek Myths, Classic Detectives, Horror and Ghosts, Seasons, Holiday Specials, Bedtime, Dice Games, Road Trip, Read-Aloud Classics, Written by players), by length (max_minutes), by what's new (new: true), by kind (mysteries, adventures, choose-your-path stories, trivia, guessing games, game shows, dice games, word games, party and storytelling games, Table Talk, Story Time read-alouds, wind-downs, open worlds and campaigns) or, within mysteries, classic or dark. Use group_by_category without a page for the whole catalogue under kind headings.

Input Schema

NameRequiredDescriptionDefault
newNoTrue for what's new: the newest pieces first, with their What's New line
kindNoOnly list this kind: mystery, adventure, branching (choose your path), trivia, guessing (guessing games), gameshow (game shows), dice (dice games), word (word games), party (party and storytelling), talk (Table Talk), story time (read-aloud classics), winddown (wind-downs), campaign (open worlds and D&D-style campaigns), or game (every one of the game kinds above except trivia and guessing)
pageNoWhich three to read, from 1. After reading a page, if the listener says more, call again with the same filters and page + 1
genreNoWithin mysteries and adventures: murder-mystery (all murder mysteries), classic (murder mysteries that aren't dark), dark (dark murder mysteries) or adventure
audienceNoNarrow by audience: general, or the all-ages pieces. Omit for everything
collectionNoA collection, by name or id, loosely matched: greek-myths, classic-detectives, ghost-gothic, seasons, holidays, bedtime, dice, road-trip, classics, players. Say "Greek Myths" or "detective stories" as the listener did.
not_playedNoTrue to leave out what this player has already played (signed-in players only)
max_minutesNoOnly pieces this many minutes long or shorter
group_by_categoryNoTrue, with no page, for the whole list grouped under kind headings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / collection / description
      Previous value: -"A collection, by name or id, loosely matched: greek-myths, classic-detectives, ghost-gothic, seasons, holidays, bedtime, dice, road-trip, classics. Say \"Greek Myths\" or \"detective stories\" as the listener did."New value: +"A collection, by name or id, loosely matched: greek-myths, classic-detectives, ghost-gothic, seasons, holidays, bedtime, dice, road-trip, classics, players. Say \"Greek Myths\" or \"detective stories\" as the listener did."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results arrive three at a time with a one-line pitch, and the page argument walks forward. It stops short of describing the exact response object or what happens at the end of the catalogue.

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?

Front-loaded with the core purpose and pagination rule, which is good, but the middle is one long run-on enumeration that largely duplicates the enum values already in the schema. The collection and kind lists could be trimmed without losing information an agent needs.

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 9-parameter, all-optional read tool with no output schema and full annotation coverage, the description covers pagination flow, grouping behavior, and every filter family. An agent could call it correctly from this text; only the end-of-list and return-shape details are missing.

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 every parameter is already documented with enums and bounds. The description mostly restates those filters (collection names, kinds, max_minutes) rather than adding syntax or edge-case meaning. Baseline 3 applies when the schema does the heavy lifting.

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 ('Lists the Plot Speaks stories and games that can be played by voice') plus the exact result shape ('three at a time with a one-line pitch each'). That distinguishes it cleanly from siblings like pick_for_me and start_story, which select or launch rather than enumerate.

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 concrete usage contexts: narrow by collection/length/new/kind, and 'use group_by_category without a page for the whole catalogue under kind headings.' It does not explicitly say when to prefer pick_for_me or start_story instead, so there is a gap, but the browsing-vs-selection boundary is strongly implied.

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

All Plot Speaks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources