Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_schedule

Fetch Sportskeeda fixtures and results by host-free slug, returning match details like teams, time, score, and venue for cricket/football, or table data for other sports.

Instructions

Get Sportskeeda fixtures and results. Returns a Sportskeeda fixtures or schedule page by host-free slug, such as nfl/schedule or cricket/schedule. Cricket and football give matches with teams, time, status, score, competition, venue and result; other sports give tables with columns and rows. An empty fixture widget returns status no_matches.

Input Schema

NameRequiredDescriptionDefault
slugYesSportskeeda schedule path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

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 two distinct response shapes (matches for cricket/football, tables for other sports), the concrete fields returned, and the empty-state signal (status 'no_matches'). It omits anything on rate limits, auth, or pagination, which keeps 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.

Conciseness5/5

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

Four sentences, front-loaded with purpose, then input form, then response shapes, then the edge case. No redundancy and every sentence carries information an agent needs.

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, the description does the heavy lifting by explaining the two return variants and the empty case, which is good. It could still say where valid slugs come from (a listing/sitemap sibling) to be fully self-sufficient.

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?

Schema coverage is 100% so the baseline is 3, but the description goes beyond the schema by giving concrete example slug values ('nfl/schedule', 'cricket/schedule') and noting the slug is host-free, which clarifies format the schema only gestures at.

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 ('Get') and resource ('fixtures and results') and further pins down the scope by naming the exact input form (host-free slug like 'nfl/schedule'). An agent can distinguish this from sibling tools such as sportskeeda_standings or sportskeeda_cricket_match 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the fixture/results framing but there is no explicit when-to-use guidance, no exclusions, and no named alternative (e.g., when to prefer sportskeeda_standings or sportskeeda_event_calendar). Adequate but leaves routing to inference.

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