Crawlora MCP

sportskeeda_nba_queries

Read-only

List the complete Sportskeeda NBA player-query directory by the live Player Stats or Player vs Team category. Returns paginated host-free slugs; pass a slug to sportskeeda_page_data for its stats table.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sportskeeda_nba_queries"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size; 0 or omitted defaults to 100, maximum is 500
`offset`	No	Zero-based result offset
`category`	No	Optional category id. Documented values: player-stat, player-vs-team.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / category / description

Added value: +"Optional category id. Documented values: player-stat, player-vs-team."

addedInput schema / properties / limit / description

Added value: +"Page size; 0 or omitted defaults to 100, maximum is 500"

addedInput schema / properties / offset / description
```
Added value: +"Zero-based result offset"
```

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results are paginated and are 'host-free slugs', which is useful format context, but discloses nothing about rate limits, auth, or result volatility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, followed by the downstream action. No filler and nothing redundant.

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 a complete schema, an output schema, and read-only annotations, the description is nearly complete: it says what is listed, how it's scoped, what form the output takes, and where to go next. The only gap is not clarifying behavior when category is omitted.

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 coverage is 100%, so limit, offset, and category are fully documented in the schema. The description only loosely maps the two category concepts ('Player Stats or Player vs Team') to the documented ids, adding marginal value 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 directory) and scopes it to two named categories. It positions itself relative to sportskeeda_page_data as the slug source, though it doesn't explicitly contrast with nearby siblings like sportskeeda_player_stats or sportskeeda_page_options.

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?

The second sentence gives a clear workflow: enumerate slugs here, then pass one to sportskeeda_page_data for its stats table. That is actionable routing guidance, but there is no explicit statement of when-not to use it or how it differs from the other Sportskeeda NBA tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?