Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_guessing_game

Fetches public clues and image metadata for a Sportskeeda daily player-guessing puzzle by slug and date, without revealing the answer.

Instructions

Get a Sportskeeda daily guessing-game puzzle. Returns the public clues and image metadata for a discovered player-guessing game and ISO date. The answer is omitted so the endpoint does not reveal the active puzzle solution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesPuzzle date in YYYY-MM-DD format
slugYesDiscovered host-free game page path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does useful work: it discloses that the return contains public clues and image metadata, and explicitly states the answer is omitted. What it does not cover is any auth requirement or rate-limit behavior, keeping it short of 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?

Three sentences, front-loaded with the core action, then return contents, then the deliberate omission of the answer. Every sentence earns its place, though the third slightly restates the second's point about not revealing the solution.

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?

No output schema exists, and the description compensates by naming what is returned (public clues, image metadata) and what is withheld (the answer). For a simple two-param read tool this is nearly complete, missing only edge-case behavior for invalid slugs or future dates.

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%, with the slug enum and the YYYY-MM-DD format both documented in the schema. The description adds the notion of an ISO date and a 'discovered player-guessing game' path, but adds no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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+resource: 'Get a Sportskeeda daily guessing-game puzzle.' An agent immediately knows this retrieves a single puzzle. It does not, however, explicitly distinguish itself from the sibling sportskeeda_guessing_games (plural) or sportskeeda_guessing_game_entities, leaving some ambiguity about which to call.

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 phrase 'for a discovered player-guessing game and ISO date' implies the tool requires a slug and date, which aligns with the required params, but there is no explicit when-to-use statement or routing to alternatives such as sportskeeda_guessing_games. Usage is inferred rather than stated.

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

Deploy Server

Other Tools