List Sportskeeda Wiki projects and retrieve live-verified slugs plus taxonomy mappings for category, catalog, and article endpoints.
List Sportskeeda Wiki projects. Returns the live-verified project slugs and taxonomy mappings accepted by the Wiki category, catalog, and article endpoints.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read-only operation and it discloses that results are 'live-verified', but it says nothing about auth needs, caching, or rate limits for an endpoint with no annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with the core purpose and followed by the return value. No filler, though it could be slightly more explicit about routing to sibling endpoints.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does explain what is returned (slugs and taxonomy mappings). For a zero-parameter listing tool this is largely sufficient, though it omits any note on the shape of the taxonomy mapping objects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. It adds no misleading param claims.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List Sportskeeda Wiki projects') and clarifies the payload ('live-verified project slugs and taxonomy mappings'). It does not explicitly name sibling tools like sportskeeda_wiki_categories or sportskeeda_taxonomy_search, so differentiation is left to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Naming the category, catalog, and article endpoints implies this is a lookup/helper used before those calls, which is useful context. However, there is no explicit when-to-use or when-not guidance versus the many other sportskeeda_wiki_* siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.