Oh, my Dots!

create_cryptogram

Create a cryptogram puzzle URL. You must provide the secret sentence/message to encode (at least 5 distinct letters). The player decodes a substitution cipher to reveal this sentence. Optionally provide hint words: clues shown alongside the puzzle, in format "word: hint" (one per line), where every letter of each word must already appear in the sentence. If the user specifies a topic instead of a sentence, generate an appropriate sentence first, then call this tool with it.

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": {
      "message": "<message>"
    },
    "name": "create_cryptogram"
  }
}

Input Schema

Name	Required	Description
`message`	Yes	The secret sentence/message to encode as a cryptogram. Must contain at least 5 distinct letters.
`language`	No	Optional: Language for the cryptogram. Use the same language as the prompt. Please use ISO 639-1 codes: en, es, fr, de, pt.
`hint_words`	No	Optional: Hint words with clues shown next to the puzzle, format "word: hint" (one per line). Every letter in each word must already appear in the message. Words do not need to be uppercased. Keep hints brief, long hints take up too much space on the board.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavioral traits: the minimum of 5 distinct letters, the substitution-cipher nature of the puzzle, and the cross-parameter constraint that every hint word letter must already appear in the message. It does not address failure modes or limits, so not 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?

Front-loaded with the purpose, followed by the required input constraint, optional hints, and fallback behavior. Four dense sentences with no filler, though it is slightly verbose in places.

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?

Complete for a 3-parameter tool with no annotations or output schema: purpose, required constraint, optional hint format, and a topic-to-sentence fallback are all covered. The implied return (a puzzle URL) is stated in the first sentence, so nothing essential is missing.

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 already 100%, but the description adds cross-parameter semantics beyond the schema: the hint format is 'word: hint' one per line, and every letter of each hint word must already appear in the message. That linkage is not expressed in the schema and is genuinely useful.

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?

States a specific verb+resource ('Create a cryptogram puzzle URL') and immediately explains the mechanism (player decodes a substitution cipher). This clearly distinguishes it from siblings like create_crossword and create_word_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance: provide a sentence directly, and if the user supplies a topic instead, generate a sentence first and then call the tool. It also states the entry constraint and the optional hint_words path, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Oh, my Dots! tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?