Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_sections

Discover Sportskeeda's live parent/child navigation tree and every public sports landing URL. Maps sections, topics, and external destinations so you can locate pages for crawling or indexing.

Instructions

Discover Sportskeeda sections and topics. Returns the live parent/child navigation tree, including external destinations marked explicitly, plus every public sports landing URL from Sportskeeda's sports sitemap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.8/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 well: it discloses that the return is a 'live' parent/child navigation tree, that external destinations are marked explicitly, and that it also emits all public sports landing URLs. It omits any note on read-only nature or rate limits, but for a zero-param discovery tool the return-behavior disclosure is substantive.

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?

Two tight sentences with the core purpose front-loaded and detail following. No filler, though the second sentence is a slightly dense run-on of three return elements.

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?

No output schema, no annotations, no parameters, so the description must stand alone, and it adequately explains what the tool yields (navigation tree plus sports landing URLs). It stops short of describing output format or how external destinations are marked, a minor gap.

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 per the rubric the baseline is 4. There is nothing for the description to add on parameter meaning, and it correctly does not invent any.

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 ('Discover Sportskeeda sections and topics') and clarifies scope by describing the navigation tree and sitemap URLs it returns. It is clearly distinguishable from article/schedule siblings, though it doesn't explicitly contrast with close siblings like sportskeeda_sitemaps or sportskeeda_taxonomy_search.

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 description implies usage (discover sections/topics) but gives no explicit when-to-use or when-not guidance and names no alternatives. With dozens of sportskeeda_* siblings, an agent gets no routing help for choosing this over the taxonomy or sitemap tools.

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