Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_event_calendar

Fetch regional Sportskeeda sports calendar events, filtered by region, sport, month, or date range, to track scheduled games and matchups.

Instructions

Get Sportskeeda regional sports calendar events. Returns all events from the embedded Sports Calendar, optionally filtered by an offered region-specific sport, one or more offered months, or an inclusive date range. Discover the current region, sport, and month values through /sportskeeda/event-calendar-options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthNoOne or more offered calendar months in YYYY-MM format; repeat this parameter for multiple months
sportNoExact sport label offered for the selected region; see event-calendar-options
regionNoCalendar region
end_dateNoInclusive range end in YYYY-MM-DD; provide together with start_date
start_dateNoInclusive range start in YYYY-MM-DD; provide together with end_date

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 behavioral burden. It discloses that all events are returned and that filtering is optional, but says nothing about result size limits, pagination, auth, or the shape of returned events.

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 core purpose followed by filter behavior and the discovery pointer. No wasted text, though the filter enumeration slightly duplicates the schema.

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 five all-optional parameters, the description adequately covers what is returned and how to bound the query, and helpfully signals that unfiltered calls return everything. It could go further on result volume/caps, but it is sufficient to invoke correctly.

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% and each parameter is already documented (including the region-dependent sport enum), so the baseline is 3. The description roughly restates the schema's filter semantics ('region-specific sport', 'offered months', 'inclusive date range') without adding format or constraint detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('Sportskeeda regional sports calendar events') and clarifies the source ('the embedded Sports Calendar'). It is clear what the tool returns, though it does not explicitly distinguish itself from sibling schedule tools like sportskeeda_schedule.

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 explains that filtering is optional and enumerates the three available filter modes (sport, months, inclusive date range), then routes the agent to /sportskeeda/event-calendar-options to discover valid filter values. It gives clear when-to-use context but does not state exclusions versus the other Sportskeeda scheduling tools.

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