Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_standings

Retrieve Sportskeeda standings or rankings from a given slug, parsing current tables. Supports an optional college basketball season and returns no_data when that season is unpopulated.

Instructions

Get Sportskeeda standings or rankings. Parses current standings tables. College basketball supports a live-discovered season value; its unpopulated current season returns status no_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSportskeeda standings or rankings path without host
seasonNoCollege basketball season starting year; live values from standings-options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavior: it reads current tables, college basketball seasons are live-discovered, and an unpopulated current season yields status no_data. It omits any auth, rate-limit, or failure context, so it is only partially transparent.

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?

Three short sentences, front-loaded with the purpose and followed by the current-tables scope and the edge case. Nothing is padded, though the phrasing is slightly terse and could be tightened.

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?

With no output schema or annotations, the description covers the core call behavior and the notable no_data edge case, which is what an agent needs for a standings fetch. Return shape details are sparse but the critical failure mode is disclosed.

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 baseline is 3, but the description adds meaning: the season enum is a college-basketball starting year whose live values are discovered via standings-options, and it explains the no_data outcome when the season is unpopulated. That is genuine context beyond the schema.

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?

States a specific verb (Get) and resource (standings or rankings), plus scoping detail that it parses current standings tables. It distinguishes itself by nature from most siblings, though it never names the closely related sportskeeda_standings_options.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance relative to alternatives. The mention that season values come from standings-options implies a companion tool but does not tell the agent when to pick one over the other.

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