Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_standings

Fetch Sportskeeda standings or rankings tables by slug, returning column labels, rows, linked cell slugs and view slugs; filter college basketball results by starting season.

Instructions

Get Sportskeeda standings or rankings. Returns Sportskeeda standings or rankings tables for a host-free slug, such as nfl/standings, with column labels, rows, linked cell slugs and view slugs. season (starting year, 2013 to 2026) applies only to college basketball standings. The current college basketball season returns status no_data with empty tables.

Input 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

A3.8/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 return shape (column labels, rows, linked cell slugs, view slugs) and a real edge case (current college basketball season returns status `no_data` with empty tables). It does not cover auth, rate limits, or error behavior, keeping it just 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?

Three tight sentences, front-loaded with the core purpose and then the return shape and the season caveat. No filler, though the opening sentence slightly overlaps the second.

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 tool with no output schema, the description covers purpose, parameter scoping, return fields, and a notable no_data edge case. It is essentially complete, though it could note pagination or row limits if any exist.

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% (baseline 3), and the description adds real meaning: `slug` is host-free with an example path, and `season` is scoped to college basketball standings only. This goes beyond the schema's terse field descriptions.

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 ('Sportskeeda standings or rankings') and gives a concrete slug example ('nfl/standings'), so the agent knows exactly what data this returns. It does not explicitly differentiate itself from sibling tools like sportskeeda_standings_options or sportskeeda_player_stats, which keeps it from a 5.

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 rather than directed: it explains that `season` applies only to college basketball standings, which tells the agent when that parameter is relevant, but there is no explicit when-to-use vs alternatives guidance (e.g., pointing to standings_options for enumerating valid sligs).

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