Skip to main content
Glama

Pick something for me

pick_for_me
Read-onlyIdempotent

Picks ONE Plot Speaks story or game to play now, ranked from the player's mood, the time they have, how many are playing and an optional collection, skipping what a signed-in player has already played. Returns the pick's title, slug and one-line pitch, plus a runner-up. Records only anonymous counts of the mood matched and length asked for. If nothing fits every filter it says so instead of picking. 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": "pick_for_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoThe mood or kind of thing, in their words, e.g. spooky, light, a mystery, something calm
minutesNoHow long they have
playersNoHow many are playing
all_agesNoTrue to keep it suitable for every age (nothing rated above PG)
collectionNoOnly from this collection, by name or id: Murder Mysteries, Greek Myths, Classic Detectives, Horror and Ghosts, Seasons, Holiday Specials, Bedtime, Dice Games, Road Trip, Read-Aloud Classics, Written by players

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / collection / description
      Previous value: -"Only from this collection, by name or id: Murder Mysteries, Greek Myths, Classic Detectives, Horror and Ghosts, Seasons, Holiday Specials, Bedtime, Dice Games, Road Trip, Read-Aloud Classics"New value: +"Only from this collection, by name or id: Murder Mysteries, Greek Myths, Classic Detectives, Horror and Ghosts, Seasons, Holiday Specials, Bedtime, Dice Games, Road Trip, Read-Aloud Classics, Written by players"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, but the description adds substantial behavior beyond them: the ranking factors, the exclusion of already-played titles for signed-in players, the return shape (title, slug, one-line pitch, plus a runner-up), an anonymous telemetry side effect, and graceful no-match handling. It also discloses a hidden interaction convention (no 'let me check' preamble, never mention the tool), which an agent could not infer elsewhere.

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, then ranking, return value, side effect, fallback, and invocation rule in a logical order. Slightly padded by the verbatim list of forbidden filler phrases, which could be compressed, but nothing is redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description covers the return payload (title, slug, pitch, runner-up) and the no-match outcome. For a zero-required-parameter, closed-world read tool, everything an agent needs to call and interpret it is present.

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 the parameter meanings are already documented. The description restates mood/time/players/collection as ranking inputs and flags collection as optional but adds no syntax, format, or edge-case detail (e.g., what happens with an unmatched collection name) beyond the schema. Baseline 3 is appropriate.

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 — picks ONE Plot Speaks story or game to play now — and enumerates the ranking inputs (mood, time, player count, collection) plus the skip-already-played scoping rule. This is clearly a recommendation/pick tool, distinguishable from list_stories or choose without opening any 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?

Gives clear usage context: use it when the player wants something to play right now, with an explicit fallback ('if nothing fits every filter it says so instead of picking') and an invocation rule ('call it silently'). It does not explicitly name when to prefer a sibling like list_stories or choose, so it stops short of full alternative routing.

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