Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_standings_options

Discover available seasons and conferences for Sportskeeda college basketball standings. Provide the required standings slug and optional season to retrieve valid conference names and slugs.

Instructions

Discover Sportskeeda college standings seasons and conferences. Lists the seasons and conferences available for Sportskeeda college basketball standings. slug is required and must be college-basketball/college-basketball-standings. Without season you get all offered season years and the current season's conferences; with it, that season's conferences, each with a name and a slug usable as the standings slug.

Input Schema

NameRequiredDescriptionDefault
slugYesCollege basketball standings slug
seasonNoA live-offered starting year; selects its conference list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden and does reasonably well: it discloses the conditional return shape (all seasons + current conferences without `season`; a single season's conferences with it) and the fields returned (name, slug). It omits any mention of auth, rate limits, or error behavior, but for a read-only options lookup this is adequate context.

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?

Three sentences, front-loaded with purpose, then the hard parameter constraint, then the conditional behavior. No filler; every sentence carries information an agent needs.

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?

There is no output schema, so the description correctly explains the returned structure (season years, conferences with name and slug). Combined with the required-slug constant and season branching, an agent has everything needed to call it correctly.

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 baseline is 3, but the description adds real meaning beyond the schema: it pins `slug` to the exact literal 'college-basketball/college-basketball-standings' and clarifies what `season` selects in terms of output. This goes past what the schema descriptions convey.

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 (discover/list) and resource (college basketball standings seasons and conferences), and frames it as an options/discovery tool distinct from the actual standings sibling. An agent can tell this is a metadata/preflight tool rather than a data-retrieval tool.

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?

Explains the required fixed `slug` value and the branching behavior of `season`, which effectively tells the agent when to include it. It hints at downstream use ('slug usable as the standings slug') but never explicitly names the alternative sibling to call afterward, so it is clear context without explicit alternative routing.

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