Zovo Word Guess

Show word puzzle

show_word_puzzle

Read-only

Use this when the user wants to play a word-guessing puzzle in the chat: either a puzzle share link someone sent them (made with this app), or a random common five-letter word ('unlimited' practice). Shows a playable grid with six guesses; the answer is not included in the reply to you. Does not open puzzles from other websites and does not reveal answers or give hints.

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

Input Schema

Name	Required	Description	Default
`puzzle_link`	No	A puzzle share link made by this app, e.g. https://word-guess.zovo.one/dl/play/s.AbC123... Leave it out to play a random common 5-letter word.

Output Schema

Name	Required	Description	Default
`note`	Yes
`title`	Yes
`source`	Yes
`letters`	Yes
`downloads`	Yes
`share_url`	Yes
`guess_rule`	Yes
`max_guesses`	Yes
`has_secret_message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds real behavior beyond the annotations: an interactive grid with six guesses, the answer deliberately withheld from the reply, no hints, and rejection of foreign links. These are non-obvious interaction traits that the readOnly/idempotent hints alone would not convey, and they are consistent with a non-idempotent random-word mode.

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?

Front-loads the trigger, then the mechanism, then the negative constraints. Three tight sentences with no repetition of the title or schema.

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

Completeness5/5

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

An output schema exists, so return structure needn't be explained, and the annotations cover the safety profile. The description still covers the one thing an agent might otherwise get wrong: that the answer will not be visible, so it should not promise the user a solution.

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 100%, so baseline is 3; the description goes slightly beyond by framing the parameter as two modes and constraining links to ones 'made with this app', which tells the agent which link values are valid to pass. It still does not restate the maxLength or format of the link 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?

Specific verb and resource: shows a playable six-guess grid for either a share link or a random five-letter word. The two modes are clearly stated, which implicitly separates it from a puzzle-generator sibling, but generate_word_puzzle is never named so the boundary must be inferred.

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

Usage Guidelines4/5

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

Explicit trigger ('when the user wants to play a word-guessing puzzle in the chat') plus clear exclusions ('does not open puzzles from other websites'). It stops short of naming the sibling generate_word_puzzle as the alternative for creating a new shareable puzzle, so the routing is clear but not complete.

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

All Zovo Word Guess 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?