Crawlora MCP

sportskeeda_wiki_pages

Read-only

Search and paginate Sportskeeda Wiki pages with live-verified sorting and page-size filters. Use a discovered project slug and pass a returned path_slug to article or community tools.

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": {
      "wiki": "<wiki>"
    },
    "name": "sportskeeda_wiki_pages"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based catalog page
`sort`	No	Sort direction. Documented values: ASC, DESC.
`wiki`	Yes	Project slug returned by sportskeeda-wiki-options. Documented values: minecraft, terraria, naruto, tiktok, youtube, gta, one-piece, sk-communities.
`limit`	No	Items per page
`search`	No	Title or page search text; sent upstream as searchText
`sort_by`	No	Catalog field to sort by. Documented values: last_updated, page_size, ratings, issues_count.

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.

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / limit / description
```
Added value: +"Items per page"
```
addedInput schema / properties / page / description
```
Added value: +"1-based catalog page"
```

addedInput schema / properties / search / description

Added value: +"Title or page search text; sent upstream as searchText"

addedInput schema / properties / sort / description

Added value: +"Sort direction. Documented values: ASC, DESC."

addedInput schema / properties / sort_by / description

Added value: +"Catalog field to sort by. Documented values: last_updated, page_size, ratings, issues_count."

addedInput schema / properties / wiki / description

Added value: +"Project slug returned by sportskeeda-wiki-options. Documented values: minecraft, terraria, naruto, tiktok, youtube, gta, one-piece, sk-communities."

First observedOct 7, 2026

TDQS

A3.6/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 that results carry "live-verified" sorting and pagination, but "live-verified" is undefined and no auth, rate-limit, or staleness behavior is disclosed. Adequate but not rich behavioral context.

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?

Two front-loaded sentences with no redundancy; the core action leads and the downstream handoff follows. Slightly diluted by the vague marketing term "live-verified," but otherwise tight.

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?

An output schema exists, so return values need no explanation, and all parameters are documented. The description covers purpose, inputs source, and downstream routing, leaving only minor gaps about pagination limits and sorting defaults.

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?

Schema description coverage is 100%, so the schema already documents all six parameters including the wiki slug's permitted values. The description restates the "discovered project slug" usage and introduces path_slug, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 and resource ("Search and paginate Sportskeeda Wiki pages") plus the modifiers it honors (sorting, page-size). It implicitly positions itself as the discovery step by routing results to "article or community tools," which helps separate it from siblings like wiki_article or wiki_categories, though it doesn't name those alternatives directly.

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?

Gives clear operational context: use a discovered project slug (fleshed out in the schema as coming from sportskeeda-wiki-options) and forward the returned path_slug to article/community tools. That establishes when to reach for this tool, but there are no explicit exclusions or named alternative tools to bound it further.

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.