Skip to main content
Glama

Open Plot Speaks

open_plot_speaks
Read-onlyIdempotent

Returns the Plot Speaks welcome: a short spoken introduction, a question offering to list the stories, start one or write one, and a menu of story categories with example titles. With skip_intro the introduction is left out; with instructions it adds the how-to-play. 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": "open_plot_speaks"
  }
}

Input Schema

NameRequiredDescriptionDefault
skip_introNoTrue when the user has heard the introduction before or asks to skip it: returns only the question and the menu
instructionsNoTrue when the user asks how Plot Speaks works or wants the instructions again: adds the how-to-play

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the exact content of the return, what each flag adds or omits, and an interaction constraint not expressed anywhere in structured data (call it silently, never emit filler phrases, never mention the tool). That is substantive behavioral context an agent cannot obtain from annotations or schema.

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?

Purpose and return content are front-loaded, followed by flag behavior and the narration rule. It is somewhat long, and the four-item list of forbidden filler phrases ('let me check', 'let me check on that', 'one moment', 'hang on') is more verbose than needed, but every sentence carries information.

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?

With only two optional boolean params, no output schema, and annotations covering the safety profile, the description is nearly sufficient: it explains return content and flag effects. The remaining gap is that it never states the trigger for calling it at all (session start, greeting, or user asking what Plot Speaks is).

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 both flags are already fully documented. The description restates their effect (skip_intro drops the intro; instructions adds the how-to-play) in slightly more operational terms but adds no syntax or edge-case meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Returns the Plot Speaks welcome") and enumerates the returned content: a short spoken introduction, a question offering to list/start/write stories, and a menu of categories with example titles. That makes its role distinguishable from siblings like list_stories or start_story, though it never explicitly says it is the session-entry tool.

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?

Usage context is only implied: the name and content make it clear this is the opening call, and the two flag conditions ('heard the introduction before', 'asks how Plot Speaks works') are spelled out. There is no explicit when-to-use/when-not statement relative to alternatives such as list_stories or choose, so an agent must infer the entry-point role.

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