Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sportskeeda_page_options

Discover Sportskeeda page menus, tabs, filters, team and ranking links, and schedule views from a slug, returning live options and leaderboard slugs.

Instructions

Discover Sportskeeda page menus and filters. Returns the page's live contextual menus, team and ranking links, tabs, schedule views, and every currently offered select-filter value. Leaderboard category and metric values carry their destination slugs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSportskeeda path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must carry the full behavioral burden. It helpfully describes the returned content (menus, links, tabs, schedule views, filter values, and slug-bearing leaderboard values), but it omits whether the operation is read-only, any side effects, authentication needs, or rate limits.

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?

The description is three dense sentences with no filler, front-loaded with the tool's purpose followed by the return contents and a clarifying note about slug-bearing values. It could arguably be tightened, but every sentence contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema and no annotations, the description covers return contents reasonably well but lacks guidance on when to use it versus the many sportskeeda siblings and does not explain the slug format beyond the schema. It is adequate but not fully complete.

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%, so the input schema already documents the single 'slug' parameter as a Sportskeeda path without host. The description adds no additional parameter meaning or format details beyond what the schema provides, so the baseline score of 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?

The description states a specific verb ('Discover') and resource ('Sportskeeda page menus and filters') and enumerates the kinds of items returned. It distinguishes itself somewhat from generic page tools by focusing on menus and filters, but does not explicitly differentiate from siblings like sportskeeda_page_data or sportskeeda_football_options.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives. The description implies a discovery use case for page menus and filters, but it never names a sibling tool or states when-not to use it, leaving the agent to infer from the output list alone.

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