Crawlora MCP

sportskeeda_event_calendar

Read-only

Fetch Sportskeeda calendar events using a discovered region and optional sport, month, or inclusive date range. Use sportskeeda_event_calendar_options to find supported region and sport values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sportskeeda_event_calendar"
  }
}

Input Schema

Name	Required	Description
`month`	No	One or more offered calendar months in YYYY-MM format; repeat this parameter for multiple months
`sport`	No	Exact sport label offered for the selected region; see event-calendar-options. Documented values: NFL, Football, MLB, College Football, NBA, College Basketball, NHL, WNBA, Golf, Tennis, NASCAR, WWE, Boxing, UFC, MMA, Formula 1, College Baseball, IndyCar, AEW, MotoGP, Wrestling, Cricket, Table Tennis, Chess, Kabaddi, Hockey, Badminton, Athletics.
`region`	No	Calendar region. Documented values: us, india.
`end_date`	No	Inclusive range end in YYYY-MM-DD; provide together with start_date
`start_date`	No	Inclusive range start in YYYY-MM-DD; provide together with end_date

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.

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / end_date / description

Added value: +"Inclusive range end in YYYY-MM-DD; provide together with start_date"

addedInput schema / properties / month / description

Added value: +"One or more offered calendar months in YYYY-MM format; repeat this parameter for multiple months"

addedInput schema / properties / month / items / description

Added value: +"Documented values: 2026-09, 2026-10, 2026-11, 2026-12."

addedInput schema / properties / region / description

Added value: +"Calendar region. Documented values: us, india."

addedInput schema / properties / sport / description

Added value: +"Exact sport label offered for the selected region; see event-calendar-options. Documented values: NFL, Football, MLB, College Football, NBA, College Basketball, NHL, WNBA, Golf, Tennis, NASCAR, WWE, Boxing, UFC, MMA, Formula 1, College Baseball, IndyCar, AEW, MotoGP, Wrestling, Cricket, Table Tennis, Chess, Kabaddi, Hockey, Badminton, Athletics."

addedInput schema / properties / start_date / description

Added value: +"Inclusive range start in YYYY-MM-DD; provide together with end_date"

First observedOct 7, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and external-scope profile. The description adds that region is 'discovered' (a prerequisite), but says nothing about pagination, result limits, or output shape. Given annotations carry the safety burden, a 3 is appropriate – modest added context but no rich behavioral detail.

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 tight sentences, zero boilerplate, and the prerequisite (region discovery) is front-loaded alongside the purpose. Every clause earns its place.

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 return values need not be explained, and annotations cover safety. The description covers the discovery prerequisite and the filter axes. It could mention what happens if no region is supplied (all regions? error?), but it is otherwise complete for a read-only calendar fetch.

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 schema already documents formats and documented values (YYYY-MM months, YYYY-MM-DD dates, exact sport labels). The description adds the meaningful causal constraint that region/sport are discovered rather than arbitrary, which is not evident from the schema. Slight value-add over the baseline 3.

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+resource ('Fetch Sportskeeda calendar events') and immediately names the scope controls (region, sport, month, date range). This distinguishes it from sibling sportskeeda_schedule and sportskeeda_college_basketball_schedule, which cover different calendars.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent to sportskeeda_event_calendar_options to discover supported region and sport values, which is the necessary prerequisite step before calling this tool. The usage condition is stated rather than implied.

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.