Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_wiki_summary

Fetch community counts for a Sportskeeda Wiki article using its slug; get accepted contributor totals, activity metrics, and open-issue count in JSON.

Instructions

Get community counts for a Sportskeeda Wiki page. Returns accepted contributor and activity totals plus the open-issue count for one Wiki article. The source page slug is obtained from sportskeeda-wiki-pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesHost-free Wiki page path_slug from sportskeeda-wiki-pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/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 what the tool returns (contributor/activity totals plus open-issue count), which is genuinely useful behavioral context. However, it does not confirm read-only nature, permissions, or any rate/access constraints, so the safety profile must be inferred from the verb 'Get'.

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?

Two sentences, zero waste, front-loaded with the purpose and then the return contents. The dependency note is short and placed last where it is useful.

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 one-parameter read tool with no output schema and no annotations, the description covers purpose, returned values, and slug provenance adequately. It stops short of defining terms like 'activity totals' or 'accepted contributor' precisely, which is the only real gap.

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 coverage is 100% and the single slug parameter is well documented in the schema. The description reinforces the source of the slug (sportskeeda-wiki-pages) but adds no format or syntax detail beyond what the schema already provides, so 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?

States a specific verb and resource ('Get community counts for a Sportskeeda Wiki page') and enumerates the returned data: accepted contributor totals, activity totals, and open-issue count. This clearly distinguishes it as an aggregate/summary tool versus detail siblings like sportskeeda_wiki_contributors or sportskeeda_wiki_issues, though it never names those alternatives.

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 only usage guidance is the data-dependency hint that the slug comes from sportskeeda-wiki-pages. There is no explicit statement of when to prefer this summary over the more granular wiki tools, nor any exclusions. Usage is implied rather than directed.

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