Skip to main content
Glama

YesNoMystery Lateral Thinking Puzzles

Get Puzzle Details & Progress

ynm_get_puzzle
Read-onlyIdempotent

Fetch one lateral thinking puzzle scenario, investigation question targets, your current progress (0–120 scale; reaching 100 unlocks free solution reveal), unlocked clues so far, and the current credit price to reveal the solution.

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_get_puzzle"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description adds real domain behavior: a 0–120 progress scale, the 100 threshold that unlocks a free solution reveal, and that a credit price for revealing is returned. This is substantive context an agent cannot get from the structured fields; only error behavior for bad IDs or locale fallbacks is left unstated.

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?

One dense sentence, front-loaded with the action and resource, then the payload. Every clause carries distinct information (progress scale, unlock threshold, credit price); the parenthetical is well-placed rather than buried, and there is no filler.

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 no output schema, the description correctly absorbs the return-value burden by enumerating the payload fields, and it explains the progress/credit mechanics that drive the puzzle loop. It falls slightly short on edge cases such as invalid puzzle_id handling or official-vs-UGC source resolution, which matter given the optional source hint.

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 the source enum are already fully documented in the schema. The description reinforces that a single puzzle is fetched but adds no format hints, precedence rules for the source hint, or locale fallback behavior beyond 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?

"Fetch one lateral thinking puzzle scenario" pairs a specific verb with a specific resource, and the enumeration of returned fields (scenario, question targets, progress, unlocked clues, reveal price) makes the tool's role unmistakable. It does not explicitly name siblings like ynm_search_puzzles or ynm_reveal_solution, though the mention of "credit price to reveal the solution" implicitly signals that reveal is a separate action.

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 only implied: an agent can infer this is the inspection/status call for a known puzzle, and the progress-scale note hints at the loop toward a free reveal. There is no explicit statement of when to prefer this over ynm_ask_question or ynm_search_puzzles, and no preconditions (e.g., needing a valid puzzle_id from search) are given.

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.