Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_standings

Read-only

Get Sportskeeda rankings and standings by host-free slug; college basketball also accepts a season discovered through sportskeeda_standings_options.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "sportskeeda_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSportskeeda standings or rankings path without host
seasonNoCollege basketball season starting year; live values from standings-options. Documented values: 2026, 2025, 2024, 2023, 2022, 2021, 2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / season / description
      Added value: +"College basketball season starting year; live values from standings-options. Documented values: 2026, 2025, 2024, 2023, 2022, 2021, 2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013."
    • addedInput schema / properties / slug / description
      Added value: +"Sportskeeda standings or rankings path without host"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered and the bar is lower. The description still adds the non-obvious 'host-free slug' constraint, which directly affects how the caller must format input. It does not describe rate limits or return shape, but an output schema exists.

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?

A single, front-loaded sentence with no filler. Every clause earns its place: the resource, the slug constraint, and the season exception with its discovery route.

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 an output schema, full parameter description coverage, and annotations covering safety, the description only needs to add routing and constraint context, which it does. Minor gap: it does not clarify the relationship to other rankings/standings siblings in the catalog.

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. The description goes beyond the schema by tying the season parameter specifically to college basketball and pointing to sportskeeda_standings_options for live values, which the schema alone does not convey.

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 (Get) and resource (rankings and standings) and adds the mechanism (host-free slug). It partially distinguishes from siblings by naming sportskeeda_standings_options, but does not clarify how it differs from peers like sportskeeda_nba_queries or sportskeeda_schedule.

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?

It gives concrete usage context: 'college basketball also accepts a season discovered through sportskeeda_standings_options,' which routes the agent to the right helper for season values. It stops short of stating when this tool should be preferred over other rankings/standings siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources