Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_quizzes

List public quiz cards for a chosen Sportskeeda category by category slug, so you can browse quizzes within anime, cricket, movies, and other topics.

Instructions

List quizzes in a Sportskeeda category. Returns public quiz cards for one category path discovered through /sportskeeda/quiz-categories. The source currently renders its first quiz page; page pagination is not exposed because the visible page links currently repeat the same cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSportskeeda quiz category path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and delivers: it discloses the return type (public quiz cards), that only the first page is rendered, and the reason pagination is unavailable (repeated links). This is genuinely useful behavioral context beyond the schema.

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 purpose, followed by return format and the pagination caveat. Each sentence is relevant, though the pagination explanation is slightly wordier than needed.

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 or annotations exist, so the description must cover returns and behavior; it explains the card output and pagination limitation adequately for a one-parameter list tool. Minor gaps remain around freshness/caching but the essentials are covered.

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% with a single enumerated 'slug' parameter fully documented in the schema. The description adds only 'one category path' framing, so baseline 3 applies since the structured field does the heavy lifting.

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 ('List quizzes in a Sportskeeda category') with clear scope limited to one category path. The reference to the /sportskeeda/quiz-categories route implicitly distinguishes it from the sibling that enumerates categories themselves.

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?

Tells the agent the category path comes from /sportskeeda/quiz-categories, giving a clear prerequisite and sourcing context. It does not explicitly contrast with sportskeeda_quiz or state when-not-to-use, so it falls short of full alternative routing.

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