Skip to main content
Glama

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. With group_by_category and no page it returns the whole catalogue under kind headings. An unknown kind or collection returns a message naming the valid ones. 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": "list_stories"
  }
}

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 page of three to return, from 1; page 2 gives items 4 to 6 of the same filtered list. Each result states the page and total pages
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. Examples: "Greek Myths", "detective stories".
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. Changed2 schema fields 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, players. 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. Examples: \"Greek Myths\", \"detective stories\"."
    • changedInput schema / properties / page / description
      Previous value: -"Which three to read, from 1. After reading a page, if the listener says more, call again with the same filters and page + 1"New value: +"Which page of three to return, from 1; page 2 gives items 4 to 6 of the same filtered list. Each result states the page and total pages"
  2. 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."
  3. First observed

TDQS

A4.2/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 adds real behavior beyond that: fixed page size of three, how the page argument maps to the next three, the interaction between group_by_category and page, and an error message naming valid kinds. The 'call it silently' clause discloses a presentation constraint not visible in annotations.

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?

It is front-loaded, with the core behavior and pagination model stated first, which is good. However, the eleven collections and roughly fifteen kinds are listed at length and essentially restate the schema's enum and collection descriptions, making the paragraph dense without adding information. The two-sentence 'call it silently' instruction is useful product behavior but contributes to the bulk.

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 nine-parameter, zero-required, read-only listing tool with no output schema, the description covers return shape (three items with pitches), pagination, the full-catalogue mode, and error behavior. The one gap is the audience and not_played filters, which the description never mentions despite them changing results materially.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds cross-parameter meaning the schema does not: page returns the next three within the same filtered list, and group_by_category only takes effect with no page. The long collection and kind enumerations are largely duplicated from the schema, which limits the additional value.

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?

The description opens with a specific verb and resource ("Lists the Plot Speaks stories and games that can be played by voice") and immediately pins down the return shape (three at a time, one-line pitch each, paginated). An agent can tell this is the catalogue-browsing tool distinct from pick_for_me or start_story without opening the schema.

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?

It gives concrete conditions for narrowing (collection, max_minutes, new, kind, genre) and explains the special mode: group_by_category with no page returns the whole catalogue under kind headings. It also states the failure path for an unknown kind or collection. What's missing is any explicit routing against siblings such as pick_for_me or a search-style alternative — the agent must infer that this is the browse path.

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