Skip to main content
Glama

Full reveal

reveal_solution

Returns the full solution of a Plot Speaks mystery (who did it, why, and the clues that pointed there) and what became of each character. Without gave_up: true it is refused unless an accusation is already recorded for that play; with gave_up: true it answers at once. Records that the play ended in a reveal. 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": "reveal_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe story slug
gave_upNoTrue when the player has said they give up or want the answer without accusing anyone
play_idYesThe play id from start_story

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description adds the substantial context behind that write flag — the tool records that the play ended in a reveal — plus the refusal precondition and an explicit delivery constraint about not narrating the call. That is exactly the kind of behavior annotations cannot convey.

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 gating conditions are correctly front-loaded, but the closing sentence is bloated, listing near-duplicate filler phrases ("let me check" and "let me check on that") instead of stating the rule once. The result is longer than needed for the information delivered.

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 terminal reveal with three parameters and no output schema, the description covers what is returned, the precondition, and the state side effect — enough to call it correctly. Only the shape or ordering of the returned solution is unspecified, which is minor given no output schema exists.

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 goes beyond the schema's definition of gave_up by stating its consequence: true answers at once, absent means refusal without a prior accusation. slug and play_id are left to the schema, which already documents them adequately.

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 states a specific verb and resource — returns the full solution of a Plot Speaks mystery, enumerating the content (who did it, why, the pointing clues) and the per-character outcome. It also distinguishes this terminal reveal from the accusation flow by naming the gating condition, so an agent can tell it apart from check_accusation and the game_* siblings.

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 an explicit when/when-not rule: refused unless an accusation is already recorded, unless gave_up is true, in which case it answers immediately. That is a real routing condition rather than vague context. The only gap is that it does not name the sibling tool an agent should use to record an accusation first, leaving that path implicit.

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