Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_wiki_contributors

List public accepted contributors for a Sportskeeda Wiki article by passing its page slug, with sorting and pagination. Excludes user IP and private account fields.

Instructions

List contributors to a Sportskeeda Wiki page. Returns public accepted contributors for one Wiki article. The source page slug is obtained from sportskeeda-wiki-pages; user IP and private account fields are never returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page
slugYesHost-free Wiki page path_slug from sportskeeda-wiki-pages
sortNoSort direction
limitNoContributors per page
sort_byNoContributor sort field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and delivers meaningful context: it returns public accepted contributors only, one article at a time, and explicitly excludes user IP and private account fields. This privacy/scope disclosure is valuable, though it omits pagination behavior and auth requirements.

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?

Three compact sentences, front-loaded with the core action and scope. The first two sentences overlap slightly ("List contributors" / "Returns public accepted contributors"), a minor redundancy, but overall efficient.

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?

No output schema exists, so the description must characterize returns, and it does so by specifying 'public accepted contributors' and the omitted private fields. Combined with page/limit params, an agent has enough to call it correctly, though return shape and pagination are not detailed.

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 five parameters including the slug enum-free format and sort options. The description adds no parameter detail beyond restating the slug's provenance, so baseline 3 is appropriate.

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?

The description states a specific verb+resource ("List contributors to a Sportskeeda Wiki page") and narrows scope to one Wiki article. It clearly distinguishes the contributors resource, though it never explicitly contrasts itself with other sportskeeda_wiki_* 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?

It provides a useful prerequisite by stating the slug comes from sportskeeda-wiki-pages, which helps an agent wire the call. However, there is no explicit guidance on when to use this versus other wiki tools or any exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools