Crawlora MCP

sportskeeda_page_options

Read-only

List Sportskeeda page-option records for live menus, teams, rankings, tabs, schedules, and currently offered select-filter values using page slug. Use sportskeeda_page_data to fetch that page or sportskeeda_football_options/sportskeeda_standings_options for sport-specific selectors.

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_page_options"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Sportskeeda path without host

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / slug / description
```
Added value: +"Sportskeeda path without host"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds scope context (that the options reflect 'currently offered' select-filter values), but says nothing about pagination, freshness, or output shape beyond what annotations and the output schema provide.

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?

Two tight sentences: the first front-loads what the tool returns, the second handles routing to alternatives. No filler or redundant restatement of the name.

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 present, return values need not be explained, and annotations cover the read-only/open-world profile. Purpose and sibling routing are covered; only minor behavioral detail (e.g., how fresh the 'currently offered' values are) is 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?

Only one parameter with 100% schema description coverage ('Sportskeeda path without host'), so the schema carries the semantics. The phrase 'using page `slug`' merely restates the schema rather than adding format examples or path conventions, matching the baseline for fully documented params.

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 ('List') plus the resource ('Sportskeeda page-option records') and then enumerates the concrete contents (live menus, teams, rankings, tabs, schedules, select-filter values). It also names the sibling tools it is distinct from, so an agent can differentiate it without opening any 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?

Explicitly routes the agent: use sportskeeda_page_data to fetch the page itself, and sportskeeda_football_options/sportskeeda_standings_options for sport-specific selectors. The alternatives are named and the selection condition is largely implied, but no explicit 'when not to use this' statement is given.

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

All Crawlora MCP tools Inspect

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

Need Help?