Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_guessing_games

List Sportskeeda player-guessing games and retrieve each game's name, slug, and game_slug. Use the returned slug with the guessing-game endpoints to access players or entities.

Instructions

List Sportskeeda player-guessing games. Lists the player-guessing games currently linked on Sportskeeda. Each has a display name, a host-free page slug such as wwe/brainbuster-wwe-player-guessing-game, and its game_slug. Pass slug to /sportskeeda/guessing-game or /sportskeeda/guessing-game-entities. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It helpfully describes the return shape (name, slug, game_slug) and scopes the listing to games 'currently linked', but says nothing about pagination, ordering, auth needs, or rate limits. For a zero-parameter read this is adequate but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are near-duplicates ('List Sportskeeda player-guessing games' vs 'Lists the player-guessing games currently linked on Sportskeeda'), so one sentence of the short description is wasted. The remaining content is front-loaded and useful, but the redundancy costs points.

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?

With zero parameters and no output schema, the description supplies the return-field shape and the downstream tool chain, which is what an agent needs. It falls just short of full completeness by omitting ordering/pagination behavior for a list endpoint.

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?

The schema has zero parameters, which sets the baseline at 4. The description explicitly confirms 'Takes no parameters', aligning with the schema and removing any doubt about how to invoke it.

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 ('List') and resource ('Sportskeeda player-guessing games') and distinguishes itself from the singular siblings sportskeeda_guessing_game and sportskeeda_guessing_game_entities by naming them as downstream consumers. An agent can identify the tool without opening the schema.

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?

Explicitly says what to do with the result: pass `slug` to /sportskeeda/guessing-game or /sportskeeda/guessing-game-entities. This routes the agent to the correct follow-up tool and defines the chaining condition, so no inference is required.

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