Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_nba_queries

List and page through Sportskeeda NBA player query pages, returning host-free slugs for player stats tables. Filter by category and access the live directory.

Instructions

List Sportskeeda NBA player query pages. Pages through the server-rendered questions on Sportskeeda's Top NBA Queries page. Slugs are host-free and can be passed to sportskeeda_page_data for the linked player stats table. The live category directory is returned on every page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size; 0 or omitted defaults to 100, maximum is 500
offsetNoZero-based result offset
categoryNoOptional category id

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?

No annotations exist, so the description carries the full burden. It discloses useful behavior ('Pages through' implies pagination, and the live category directory is returned on every page), but omits read-only/permission semantics, rate limits, and total counts. Adequate but not rich.

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?

Three short sentences, each carrying distinct information (what it lists, the chaining slug guidance, the returned directory). Front-loaded purpose with no filler.

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?

With no output schema, the description supplies return-side context: host-free slugs and the per-page category directory. Combined with the full param coverage, an agent has nearly everything needed to call it and use results, only lacking total-count/pagination limits detail.

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%, with limit, offset, and category (enum) all documented in the schema, so the baseline is 3. The description adds no syntax or format detail beyond what the schema already provides.

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 ('List') and resource ('Sportskeeda NBA player query pages') and clarifies it pages the server-rendered questions from the Top NBA Queries page. It distinguishes itself from the sibling sportskeeda_page_data, which it explicitly routes to, so an agent can tell them apart.

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?

Explains the follow-up path: slugs are host-free and can be passed to sportskeeda_page_data for the linked player stats table. This gives clear chaining context, though it doesn't state explicit when-not-to-use conditions against other siblings like sportskeeda_page_options.

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