Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_wiki_options

List available Sportskeeda Wiki projects and their slugs to identify which wiki to query for categories and pages.

Instructions

List Sportskeeda Wiki projects. Lists the Sportskeeda Wiki projects, each with a slug, display name, taxonomy_id and taxonomy_slug. Current slugs are minecraft, terraria, naruto, tiktok, youtube, gta, one-piece and sk-communities. Use a slug with wiki-categories and wiki-pages. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.3/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 mostly meets it: it discloses the return fields (slug, name, taxonomy_id, taxonomy_slug), enumerates current slug values, and states "Takes no parameters." It omits any note on auth, rate limits, or freshness, but for a static list endpoint this is solid.

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?

Front-loaded and useful, but it restates the opening ("List Sportskeeda Wiki projects. Lists the Sportskeeda Wiki projects..."), a minor redundancy that dents an otherwise tight definition.

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?

Given no output schema and an empty parameter schema, the description usefully documents the return shape and even the concrete slug values, covering what an agent needs to call it and chain it into wiki-categories/wiki-pages.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; the description reinforces this with "Takes no parameters" and needs to add nothing further about inputs.

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 Sportskeeda Wiki projects") and enumerates the exact fields returned, making it clearly distinguishable from sibling tools like sportskeeda_wiki_pages and sportskeeda_wiki_categories.

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 routes the agent: "Use a `slug` with `wiki-categories` and `wiki-pages`," naming the downstream tools. It stops short of stating when NOT to call it, so it misses the top mark.

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