Crawlora MCP

sportskeeda_topic

Read-only

Retrieve a Sportskeeda topic, event, team, or player overview's ordered CMS body: prose, lists, tables, images and embeds. Pass a path slug from sportskeeda_sitemap_items for tags.xml, tournaments.xml, teams.xml, players.xml, or us-sitemap.xml; use sportskeeda_feed for article cards and sportskeeda_page_data for structured sports tables.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Canonical Sportskeeda topic, event, team or player 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: +"Canonical Sportskeeda topic, event, team or player path without host"
```
First observedOct 5, 2026

TDQS

A4.7/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; the description adds that the return is an ordered CMS body composed of prose, lists, tables, images and embeds. It doesn't discuss auth, rate limits, or failure modes, but the content-shape disclosure is useful context beyond the annotations.

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 dense sentences: the first front-loads the action and return shape, the second handles sourcing and alternatives. No filler and no repetition of structured fields.

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?

An output schema exists, so return values need no explanation, and the single path parameter plus its source and the sibling alternatives are fully covered. Nothing needed to invoke the tool correctly is missing.

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% and the schema describes slug as a canonical path without host, so the baseline is 3. The description adds real meaning by telling the agent where slugs come from (sportskeeda_sitemap_items tags.xml/tournaments.xml/teams.xml/players.xml/us-sitemap.xml), which the schema does not provide.

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 (Retrieve) and resource (a Sportskeeda topic/event/team/player overview's ordered CMS body), then enumerates the content types (prose, lists, tables, images, embeds). It explicitly distinguishes itself from sportskeeda_feed and sportskeeda_page_data, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives both the input source (pass a path slug from sportskeeda_sitemap_items, naming the specific sitemap files) and the alternative tools with the conditions that select them: sportskeeda_feed for article cards, sportskeeda_page_data for structured sports tables. When-to-use and when-to-use-something-else are both covered.

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?