Crawlora MCP

sportskeeda_quiz

Read-only

Fetch a Sportskeeda quiz definition and return numbered question records, types, images, time limit, and answer choices for a host-free slug from sportskeeda_quizzes. Correctness, answer checks, and user activity are excluded.

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>"
    },
    "name": "sportskeeda_quiz"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Sportskeeda quiz path without host, discovered through /sportskeeda/quizzes

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.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / slug / description

Added value: +"Sportskeeda quiz path without host, discovered through /sportskeeda/quizzes"

First observedOct 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already carry readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful scope detail by declaring that correctness, answer checks, and user activity are excluded from the payload, which the agent otherwise could not infer. It does not discuss error or miss behavior for invalid slugs.

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?

Two tightly packed sentences with no filler; the resource and return contents are front-loaded, and the exclusion clause follows. Every clause carries signal.

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 the description needn't document return structure, yet it does list the returned fields and notes the exclusions, which is sufficient for correct invocation. Minor gaps like pagination or behavior on an unresolvable slug are not addressed, but this is a simple single-param read 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?

With one parameter and 100% schema description coverage, the schema already documents the slug and its 'without host' constraint. The description's phrase 'host-free slug from sportskeeda_quizzes' largely restates the schema, adding little syntax or format detail beyond it, so the baseline 3 applies.

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 (Fetch) and resource (Sportskeeda quiz definition), and enumerates what is returned: numbered question records, types, images, time limit, and answer choices. The reference to the slug source (sportskeeda_quizzes) and the explicit exclusions (correctness, answer checks, user activity) let an agent separate this from the sibling list tool without opening a 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?

The description implies the retrieval workflow by specifying the slug must be 'host-free ... from sportskeeda_quizzes', effectively pointing to the sibling that supplies the input. It does not explicitly state when not to use it or name alternative tools for excluded data, but the context is clear enough to route correctly.

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.