Crawlora MCP

sportskeeda_wiki_contributors

Read-only

List public accepted contributors for a discovered Sportskeeda Wiki article with verified pagination and sort filters.

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

Input Schema

Name	Required	Description
`page`	No	1-based page
`slug`	Yes	Host-free Wiki page path_slug from sportskeeda-wiki-pages
`sort`	No	Sort direction. Documented values: asc, desc.
`limit`	No	Contributors per page
`sort_by`	No	Contributor sort field. Documented values: author_name, contributions, updated_at.

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.

Changed5 schema fields changedOct 7, 2026

addedInput schema / properties / limit / description
```
Added value: +"Contributors 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 / sort / description

Added value: +"Sort direction. Documented values: asc, desc."

addedInput schema / properties / sort_by / description

Added value: +"Contributor sort field. Documented values: author_name, contributions, updated_at."

First observedOct 5, 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 are limited to 'public accepted' contributors (a filtering behavior) and offers 'verified pagination', which is modest context beyond the annotations but no detail on limits, ordering guarantees, or data freshness.

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 front-loaded sentence with no filler; the resource and scope lead, and supporting details (pagination, sort) follow. Every clause carries information.

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 the 100% schema coverage covers all five parameters. The only gap is the absence of guidance about prerequisites relative to sibling tools (e.g., which tool first yields a slug), but the description is otherwise complete for a filtered read-only listing.

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%: page, slug, sort, limit, and sort_by are all documented in the schema, including the slug's provenance and the documented sort/sort_by values. The description's 'pagination and sort filters' merely restates what the schema already conveys, so the 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?

Names a specific verb (List) and resource (public accepted contributors) scoped to a discovered Sportskeeda Wiki article, which contrasts reasonably with sibling tools like sportskeeda_wiki_activity or sportskeeda_wiki_pages. It is clear but does not explicitly distinguish itself from those siblings.

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' plus the slug description ('from sportskeeda-wiki-pages') implies the tool must be called after discovering a page, giving implied usage context. However, there is no explicit when-to-use/when-not guidance or named alternative among the many sportskeeda_wiki_* siblings.

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?