Skip to main content
Glama

YesNoMystery Lateral Thinking Puzzles

Search Lateral Thinking Puzzles

ynm_search_puzzles
Read-onlyIdempotent

Search and filter official YesNoMystery puzzles and public password-free community (UGC) turtle soup mysteries across 12 languages. Never returns solutions. Supports filtering by locale, source, category, difficulty (1=easy, 2=medium, 3=hard), tags, keyword query, or random sampling.

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": "ynm_search_puzzles"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter puzzles that include all specified tags
limitNoMax puzzles to return (default 15, or 3 when random=true)
queryNoCase-insensitive keyword search on title and scenario
localeNoPuzzle language code (en, zh, zh-TW, ja, ko, de, es, fr, it, pt, ru, th). Also accepts zh-CN, en-US, ja-JP.
offsetNoPagination offset (ignored when random=true)
randomNoWhen true, return random matching puzzles
sourceNoFilter by source: all (official + public UGC), official, or ugcall
categoryNoOptional category filter
difficultyNoDifficulty tier: 1 (easy), 2 (medium), 3 (hard)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: solutions are never returned, UGC content is public and password-free (no auth needed), and coverage spans 12 languages. It stops short of describing the return shape or pagination behavior, which keeps it below a 5.

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?

Two sentences, front-loaded with the resource and scope, then the capability list. The filter enumeration largely restates schema fields, which is mild redundancy, but the text stays tight and scannable with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, zero-required search tool with no output schema, the description covers scope, sources, and the no-solutions guarantee but never says what a result actually contains (IDs, titles, snippets?) or how results are ordered. An agent can call it, but cannot predict the response well enough to plan multi-step use with ynm_get_puzzle.

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 every one of the 9 parameters is already documented in the schema, including the difficulty mapping and locale codes that the description repeats. The description adds no syntax, interaction rules (e.g. how query interacts with tags), or default behavior beyond what the schema states, so 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?

Specific verb ('search and filter') plus a clearly scoped resource: official YesNoMystery puzzles and public password-free UGC turtle soup mysteries across 12 languages. The 'Never returns solutions' line implicitly separates it from ynm_reveal_solution, but no sibling is named, so an agent must still infer that ynm_get_puzzle handles single-puzzle retrieval.

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 by the verb: call this when you want to find or filter puzzles rather than fetch one by ID or reveal an answer. There is no explicit when-to-use/when-not statement and no named alternative, so the routing decision is left to inference.

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.