Crawlora MCP

sportskeeda_wiki_summary

Read-only

Fetch public accepted-contributor, activity, and open-issue totals for a discovered Sportskeeda Wiki article. Use sportskeeda_wiki_activity, sportskeeda_wiki_contributors, or sportskeeda_wiki_pages for details.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Host-free Wiki page path_slug from sportskeeda-wiki-pages

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: +"Host-free Wiki page path_slug from sportskeeda-wiki-pages"
```
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 safety posture is covered. The description adds that the totals are 'public' and that the article must be 'discovered', which is useful framing but no richer than that.

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 sentences, zero waste. The scoping detail (which totals) is front-loaded and the alternative routing follows immediately.

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-value shape need not be described, and the description correctly frames the tool as a compact aggregate source. It is nearly complete; only explicit prerequisites (article must first be resolved via sportskeeda_wiki_pages) are left implicit.

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% for the single slug parameter, which already explains it is a host-free Wiki page path_slug from sportskeeda-wiki-pages. The description's 'discovered ... article' wording echoes this without adding format or resolution detail, so the baseline 3 applies.

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 ('Fetch') and a precisely enumerated resource ('public accepted-contributor, activity, and open-issue totals for a Sportskeeda Wiki article'). The word 'totals' distinguishes it from the detail-oriented siblings named in the same description.

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 to sportskeeda_wiki_activity, sportskeeda_wiki_contributors, or sportskeeda_wiki_pages when details (rather than totals) are wanted. Clear context, though it does not state prerequisites beyond 'discovered' article or when-not to call it at all.

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?