Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_event_calendar_options

List available Sportskeeda event calendar regions, sports, and months, then use the returned region, sport, and month values to query event-calendar data.

Instructions

Discover Sportskeeda calendar regions, sports, and months. Lists the regions (us and india) of the Sportskeeda event calendar, each with the sport names and YYYY-MM months currently on offer. Takes no parameters. Pass the exact region, sport and month values to /sportskeeda/event-calendar; no year parameter exists.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/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 discloses the key behavioral facts: it takes no parameters, returns regions (`us` and `india`), sport names, and `YYYY-MM` months, and has no year parameter. It stops short of stating safety profile, auth needs, or rate limits, keeping it from 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?

It is front-loaded with the core purpose, then efficiently lists returned fields, states the absence of parameters, and describes how to use the results. Every sentence earns its place with no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless discovery tool with no output schema and no annotations, the description provides everything needed: what it lists, the exact value formats, the absence of parameters, the lack of a year parameter, and the endpoint to pass values to next.

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?

The tool has 0 parameters, so the baseline is 4. The description adds useful format context for the values it emits (regions like `us` and `india`, months as `YYYY-MM`) and clarifies that no year parameter exists, which helps downstream calls, but there are no parameters of its own to explain.

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?

It uses a specific verb ('Discover') and names the exact resource ('Sportskeeda event calendar' regions, sports, months) and what it returns. It clearly distinguishes itself from the sibling sportskeeda_event_calendar by describing itself as the options/discovery step that supplies values to that endpoint.

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?

It states 'Takes no parameters' and directs the agent to 'Pass the exact region, sport and month values to /sportskeeda/event-calendar', which clearly explains what to do with the results and implicitly when to use this tool. It does not explicitly name alternatives or when-not to use it, so a 4 rather than 5.

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