Skip to main content
Glama

Rate a story

rate_story

Saves a rating and feedback for a Plot Speaks story the user has just played: 1 to 5 stars, whether anything was given away too early, an optional comment about the story, optional feedback about the experience for the people who make Plot Speaks, and, for a story still being tested, the player's verdict (passed, or needs work). Needs the play id from start_story; one rating per play; stars or a verdict (or both). 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "play_id": "<play_id>"
    },
    "name": "rate_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe story slug
wishNoWhat else the player would like to play, if they said, in their words
starsNo1 to 5 (optional when a verdict is given)
commentNoThe player's comment about the story, if any, in their words
play_idYesThe play id from start_story
spoiledNoTrue if the player felt the narrator gave something away too early
verdictNoFor a story being tested: "passed" if it passed the player's test, "needs_work" if something should be improved (put what, in their words, in feedback)
feedbackNoFeedback about the experience (the narration, the connector, what to improve), if any, in the player's words; read by the people who make Plot Speaks

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?

Beyond the annotations it discloses the one-rating-per-play constraint, that feedback is 'read by the people who make Plot Speaks', and that the verdict field only applies to 'a story still being tested'. It also gives explicit conversational behavior ('Call it silently... never mention the tool'), which the annotations cannot convey. It does not say what happens on a duplicate submission or whether the call is recoverable, but for a non-destructive write this is substantial added context.

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?

The purpose and constraints are front-loaded in the first sentence, but that sentence is a long comma-chained enumeration that largely restates eight fields already documented at 100% coverage in the schema. The silent-invocation sentence is valuable but padded with four near-synonymous example phrases ('let me check', 'let me check on that', 'one moment', 'hang on').

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 an 8-parameter mutation with no output schema, the definition covers the prerequisite, the uniqueness rule, the minimum payload, and the conversational framing an agent needs. The only meaningful gap is the response/error behavior when a play has already been rated, which the 'one rating per play' line raises but does not resolve.

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 the baseline is 3, but the description adds cross-parameter semantics the schema only hints at: 'stars or a verdict (or both)' resolves the optionality between the two required-ish fields. It also scopes verdict to stories under test and notes that the 'what to improve' detail belongs in feedback rather than verdict, which is genuine routing guidance not in the schema.

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 names a specific verb and resource ('Saves a rating and feedback for a Plot Speaks story the user has just played') and enumerates the payload (stars, spoiled flag, comment, feedback, verdict). It clearly separates itself from the read-side siblings by being the write-back step after a play, though it never names review_story or submit_story as the alternative for a different kind of story feedback.

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 states the precondition ('Needs the play id from start_story'), the cardinality rule ('one rating per play'), and the minimum payload ('stars or a verdict (or both)'). It stops short of any exclusion such as when to prefer review_story or what to do if the player already rated the play, so the agent must infer the failure 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