Crawlora MCP

sportskeeda_wiki_issues

Read-only

List public opened or closed issues for a discovered Sportskeeda Wiki article; private submitter IP fields are omitted.

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

Input Schema

Name	Required	Description
`page`	No	1-based page
`slug`	Yes	Host-free Wiki page path_slug from sportskeeda-wiki-pages
`limit`	No	Issues per page
`status`	No	Issue status. Documented values: opened, closed.

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.

Changed4 schema fields changedOct 7, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Issues per page"
```
- addedInput schema / properties / page / description
```
Added value: +"1-based page"
```
- addedInput schema / properties / slug / description
```
Added value: +"Host-free Wiki page path_slug from sportskeeda-wiki-pages"
```
- addedInput schema / properties / status / description
```
Added value: +"Issue status. Documented values: opened, closed."
```
First observedOct 7, 2026

TDQS

A3.8/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 the safety profile is known. The description adds genuinely useful behavioral context beyond the annotations: that only public issues are returned and private submitter IP fields are omitted. It does not mention pagination behavior, though a page/limit params exist.

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 tight sentence that front-loads the verb and resource and appends the privacy caveat. No wasted wording.

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 and annotations covering the read-only/open-world profile, the description need not explain return values. It covers the public/private filtering behavior, leaving only minor gaps such as relationship to sibling wiki tools.

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 all four parameters (slug, page, limit, status) are already documented in the schema, including that status accepts opened/closed. The description adds no parameter detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (List) and resource (issues for a discovered Sportskeeda Wiki article), and clarifies scope (public, opened or closed). Clear but does not differentiate from sibling wiki tools like sportskeeda_wiki_article or sportskeeda_wiki_activity.

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

Usage Guidelines3/5

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

The phrase 'for a discovered Sportskeeda Wiki article' implies the slug comes from a prior page discovery call, but there is no explicit when-to-use guidance or comparison to sibling wiki tools. Usage is only implied.

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.