Skip to main content
Glama

YesNoMystery Lateral Thinking Puzzles

Reveal Puzzle Solution

ynm_reveal_solution
Idempotent

Reveal the full solution and all clues for a puzzle using the same dynamic credit pricing as the website (20/30/40 credits at 0 progress, 1 credit at progress >= 80, and 0 credits FREE once progress reaches 100). Idempotent if already revealed.

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": {
      "puzzle_id": "<puzzle_id>"
    },
    "name": "ynm_reveal_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoPuzzle language code (defaults to en)
sourceNoOptional explicit source hint: official or ugc
puzzle_idYesOfficial puzzle ID/slug or public UGC puzzle UUID/slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly=false, idempotent=true, and destructive=false, and the description corroborates idempotency ('Idempotent if already revealed'). Beyond that, it adds genuinely useful context not present in structured fields: a concrete credit-cost schedule that scales with puzzle progress, including a free tier at 100%. It stops short of saying whether a reveal is permanent or how credits are deducted from the account.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and followed by the cost model and idempotency note. No filler; the parenthetical pricing detail is dense but each clause conveys operationally relevant 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?

There is no output schema, but 'full solution and all clues' gives the agent a reasonable expectation of the return payload, and the cost model covers the main non-obvious consequence of calling. Minor gaps remain around whether the reveal persists and how credit balance is affected, but nothing blocking for a 3-parameter tool.

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 puzzle_id, locale, and source are already documented in the schema, and the description does not add syntax or selection guidance for them. Baseline 3 is appropriate when the schema carries the parameter burden; the only extra hint is the implicit link between 'progress' and pricing, which no parameter exposes.

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 uses a specific verb and resource: 'Reveal the full solution and all clues for a puzzle,' which is clearly a distinct action from the sibling read/query tools (get, ask, search). It does not explicitly name a sibling to contrast with, but the scope of the operation is unambiguous.

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 is implied rather than stated: an agent can infer this is the terminal action when the user wants the answer, and the pricing tiers hint that it should be reserved for high-progress or explicit-request cases. However, there is no explicit when-not guidance (e.g., prefer ask_question for hints) and no prerequisites stated.

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.