Skip to main content
Glama

YesNoMystery Lateral Thinking Puzzles

Ask Yes/No Question

ynm_ask_question

Ask the YesNoMystery AI host a yes/no deduction question for a puzzle (costs 2 trial credits; 50 free trial credits per anonymous client). Set include_history=true (default) and pass prior Q&A turns for contextual clue tracking, or set include_history=false to judge the question standalone.

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>",
      "question": "<question>"
    },
    "name": "ynm_ask_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage code for the puzzle and AI judgment (defaults to en)
sourceNoOptional explicit source hint: official or ugc
historyNoOptional explicit Q&A history turns when include_history=true; ignored when include_history=false
questionYesYes/no deduction question or hypothesis to ask the AI host
puzzle_idYesOfficial puzzle ID/slug or public UGC puzzle UUID/slug
include_historyNoWhether to include prior Q&A history when judging this question (default true)

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 only declare the generic profile (openWorld=false, idempotent=false, destructive=false). The description adds genuinely non-obvious behavior: each call costs 2 trial credits and there is a 50-credit allowance per anonymous client, which tells the agent this is a metered, non-repeatable call. It omits auth requirements and whether questions are persisted server-side.

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?

A single tightly packed sentence that front-loads the purpose and then the cost model before the parameter advice. Every clause carries information the agent cannot get from annotations or schema, 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?

Cost, credit allowance, and history semantics are covered, and the six parameters are fully documented in the schema. Since there is no output schema, the description arguably should say what comes back — the possible referee answers (yes/no/unknown/partial_ok/irrelevant/needs_rephrase) appear only inside the nested history schema, leaving the agent to infer the return shape.

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 description coverage is 100%, so a baseline of 3 is available, and the description exceeds it by explaining the intent behind include_history: pass prior turns to track clues, or disable it to get a standalone judgment. That clarifies a strategy decision the schema only states mechanically.

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?

States a specific verb and resource: 'Ask the YesNoMystery AI host a yes/no deduction question for a puzzle', which is distinct from the sibling operations (get, reveal, search). It does not explicitly name a sibling to contrast with, so differentiation comes from the verb rather than explicit routing.

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?

The description gives tactical guidance on the include_history flag ('contextual clue tracking' vs 'judge the question standalone'), which is real when-to-use guidance at the parameter level. It offers no tool-level guidance, however, such as when to ask a question versus calling ynm_reveal_solution or ynm_get_puzzle, so the agent must infer that from the sibling names.

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.