Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_wiki_activity

Fetch the public accepted edit history for a Sportskeeda Wiki article using its page slug. Supports pagination and sorting by author or update time.

Instructions

List accepted edits for a Sportskeeda Wiki page. Returns the public accepted activity history for one Wiki article, with bounded pagination and the page's live sort fields. The source page slug is obtained from sportskeeda-wiki-pages.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: only accepted edits are returned, pagination is bounded, and live sort fields are available. It stops short of stating permission/auth requirements or explicitly confirming read-only semantics, but 'List' clearly implies a safe read.

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?

The definition is short and front-loads the purpose before the prerequisite. The second sentence partly restates the first (both say it returns the accepted activity history), which is minor redundancy but not harmful.

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?

For a no-annotation, no-output-schema, 5-parameter list tool, the description covers purpose, the required slug source, pagination bounding, and sort availability. It leaves the shape of returned activity items unspecified, but that gap is modest given the tool's simplicity.

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 five parameters (page, slug, sort, limit, sort_by) are already documented with descriptions and enums. The description adds only loose context about 'bounded pagination' and 'live sort fields' without new syntax or format details, matching the baseline 3.

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 and resource ('List accepted edits for a Sportskeeda Wiki page') and clarifies the scope as the 'public accepted activity history for one Wiki article'. This separates it from nearby siblings like sportskeeda_wiki_contributors, sportskeeda_wiki_issues, and sportskeeda_wiki_summary.

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 names the prerequisite source for the required slug ('obtained from sportskeeda-wiki-pages'), which is the key gating condition for calling it. However, it never says when to prefer this over the sibling wiki tools (contributors, issues, options), so a competing-tool decision is left to inference.

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