Crawlora MCP

sportskeeda_wiki_activity

Read-only

List public accepted edit history 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_activity"
  }
}

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	Activity items per page
`sort_by`	No	Activity sort field. Documented values: author_name, 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: +"Activity items 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: +"Activity sort field. Documented values: author_name, 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 safe-read profile is covered. The description adds 'public accepted' (implying only accepted, not pending/rejected edits) and 'verified pagination,' which is modest extra context but no detail on result volume or auth.

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?

One sentence, front-loaded with the operation and scope, no filler. Every clause (public, accepted, pagination, sort) carries meaning.

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 safety profile, the description need not explain return values. It communicates scope and that pagination/sort are supported, which is adequate for a 5-param list tool, though it omits any routing versus sibling wiki endpoints.

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%, with per-parameter descriptions for page, slug, sort, limit, and sort_by, so the schema carries the semantics. The description's 'pagination and sort filters' only gestures at params without adding format or default detail beyond the schema.

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+resource: 'List public accepted edit history for a Sportskeeda Wiki article.' The 'public accepted edit history' scope is distinctive against nearby wiki siblings (contributors, issues, summary). However, it does not explicitly differentiate itself from those siblings, so an agent must infer the distinction.

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?

'for a discovered Sportskeeda Wiki article' implies the slug comes from a discovery step (sportskeeda-wiki-pages), which is mild contextual guidance. There is no explicit when-to-use/when-not or named alternative versus sportskeeda_wiki_contributors or sportskeeda_wiki_summary.

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?