Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_quiz

Fetch a Sportskeeda quiz definition by slug to retrieve public question prompts and choice text sorted by question number, without answer data.

Instructions

Get a Sportskeeda quiz definition. Returns public question prompts and choice text from a quiz page, sorted by question number. The source does not expose correct answers in its anonymous page data; answer checking and user submissions are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSportskeeda quiz path without host, discovered through /sportskeeda/quizzes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/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 well: it discloses the return shape (prompts and choice text, sorted by question number) and, critically, negative behavior — correct answers are not exposed and answer checking/submissions are unsupported. It omits auth, rate-limit, or pagination context, 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.

Conciseness5/5

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

Three tight sentences: purpose first, then return content, then the answer-related limitation. Every sentence carries information the agent needs; nothing is redundant.

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 no output schema and no annotations, the description supplies what's needed: what is returned, its ordering, and the key limitation that answers can't be checked. For a simple single-param read tool this is nearly complete, with only minor gaps (pagination, error behavior) remaining.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'slug' fully (including the discovery source). The description adds no format or syntax detail beyond it; baseline 3 is appropriate.

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 and resource ('Get a Sportskeeda quiz definition') and immediately scopes the payload ('public question prompts and choice text, sorted by question number'). This distinguishes it from the sibling sportskeeda_quizzes (list) and sportskeeda_quiz_categories without the agent needing to open any schema.

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?

It doesn't spell out an explicit when-to-use vs sportskeeda_quizzes, but the slug description says the path is 'discovered through /sportskeeda/quizzes', which is real routing guidance that tells the agent how to obtain the input this tool requires. No exclusions or when-not guidance are given, so it falls short of a 5.

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