Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_college_basketball_schedule_options

Retrieve college basketball schedule seasons and date-picker windows from Sportskeeda, returning available options from the published minimum through the current season.

Instructions

Discover college basketball schedule seasons and date window. Reads Sportskeeda's current college basketball schedule configuration. It returns every season from the published minimum through the current schedule season and the date-picker window. The conference selector is shown by the site, but its current-season feed metadata is incomplete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoA season starting year from the live seasons list; defaults to the current schedule season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does add real value: it discloses the return contents (every season from the published minimum through the current season plus the date-picker window) and flags a concrete limitation (the conference selector's current-season feed metadata is incomplete). It does not state read-only/auth behavior, hence not 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.

Conciseness4/5

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

The first sentence front-loads the core purpose, and subsequent sentences cover return scope and a caveat. Slightly wordy across four sentences but each carries information; nothing is redundant enough to penalize heavily.

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?

For a single-optional-parameter tool with no output schema and no annotations, the description covers purpose, return scope, and a metadata caveat. It would be fully complete if it tied the returned seasons to the companion schedule-call flow.

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 description coverage is 100%, so the single optional 'season' parameter is already fully documented in the schema; baseline is 3. The description references the season concept but adds no format or constraint beyond what the schema states.

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?

The description states a specific verb and resource: it reads/discover's Sportskeeda's college basketball schedule seasons and date-picker window. It is clearly the configuration/metadata companion to sportskeeda_college_basketball_schedule, though it never names that sibling explicitly to draw the contrast.

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 (an options tool that surfaces valid seasons/date windows, presumably before requesting the actual schedule), but there is no explicit 'use this to obtain valid season values for the schedule call' or when-not guidance. The agent must infer the relationship to the sibling schedule tool.

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