Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sportskeeda_college_basketball_schedule

Get all Sportskeeda college basketball games and published scores for a specific date and season; check schedule options for valid season values.

Instructions

Get Sportskeeda college basketball games for a date. Returns all games and published scores for the requested date and season from Sportskeeda's first-party JSON feed. Discover valid season values with college-basketball-schedule-options. The upstream conference filter is currently unreliable and this endpoint does not accept it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesGame date in YYYY-MM-DD format
seasonYesSeason starting year returned by college-basketball-schedule-options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/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 data source (first-party JSON feed), that all games and published scores are returned, and flags a real behavioral quirk that the upstream conference filter is unreliable and the endpoint rejects it. Auth, rate limits, and pagination remain unstated, keeping 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.

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by return behavior, season discovery, and a caveat. Four sentences with little waste, though the caveat could be tightened slightly.

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 two-parameter read tool with no output schema or annotations, the description covers what is returned (all games and published scores), how to source the season value, and a known filter limitation. Only return-shape details and error/auth behavior are absent.

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%, with date (YYYY-MM-DD) and season documented in the schema, so the baseline is 3. The description adds the useful constraint that no conference filter is accepted, but contributes no additional format or semantics for the two parameters.

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 (Sportskeeda college basketball games) scoped to a date, and explicitly names the sibling tool for discovering season values. An agent can distinguish it from college-basketball-schedule-options without opening either schema.

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?

Clearly routes the agent to college-basketball-schedule-options to obtain valid season values, which is the key prerequisite. It does not state explicit when-not conditions or broader alternatives, but the single relevant alternative is named with its condition.

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