Crawlora MCP

sportskeeda_guessing_game

Read-only

Fetch public daily clues and image metadata for a Sportskeeda player-guessing game. Provide a current slug from sportskeeda_guessing_games and a valid YYYY-MM-DD date; the puzzle answer is omitted.

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": {
      "slug": "<slug>",
      "date": "<date>"
    },
    "name": "sportskeeda_guessing_game"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Puzzle date in YYYY-MM-DD format
`slug`	Yes	Discovered host-free game page path. Documented values: wwe/brainbuster-wwe-player-guessing-game, nfl/gridle-nfl-player-guessing-game.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / date / description

Added value: +"Puzzle date in YYYY-MM-DD format"

addedInput schema / properties / slug / description

Added value: +"Discovered host-free game page path. Documented values: wwe/brainbuster-wwe-player-guessing-game, nfl/gridle-nfl-player-guessing-game."

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, so the safety profile is set. The description adds real behavioral context: the clues and image metadata are public and the puzzle answer is deliberately omitted, which tells the agent what it will and won't receive.

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 tight sentences, front-loaded with the purpose and followed immediately by the required inputs and the omission caveat. 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?

An output schema exists, so return-value detail is unnecessary. The description covers purpose, required inputs and their source, and the notable exclusion (answer omitted), leaving no material gap for an agent calling the tool.

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 coverage is 100%, so both parameters are already documented. The description restates the inputs and adds only the qualifier that the slug must be 'current'; it contributes little beyond what the schema and its property descriptions provide, 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?

States a specific verb and resource ('Fetch public daily clues and image metadata for a Sportskeeda player-guessing game') and specifies the scope ('puzzle answer is omitted'). It doesn't explicitly differentiate itself from sibling sportskeeda_guessing_game_entities, but the described payload is concrete enough for an agent to recognize.

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?

'Provide a current slug from sportskeeda_guessing_games and a valid YYYY-MM-DD date' gives a clear prerequisite and names the sibling that supplies the slug. It lacks explicit when-not-to-use guidance, but the required input source makes the usage path unambiguous.

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

All Crawlora MCP 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?