Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_homepage_leaders

Retrieves the NBA homepage leaderboard for one stat category, such as Points or Rebounds, to identify the current top players.

Instructions

NBA homepage leader board. Returns the homepage leader board for one category. This endpoint has no required parameter beyond the league: a LeagueID-only request answers 200 and echoes its whole contract, which is how its parameter names were recovered after an earlier sampled request answered 400. Note its category spelling is the upstream's own — 'Points' and 'Rebounds', not the 'PTS' short form leagueleaders uses.

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": "nba_homepage_leaders"
  }
}

Input Schema

Name	Required	Description
`league_id`	No	League id; only 00 (NBA) is verified
`game_scope`	No	Game window
`player_scope`	No	Player pool
`stat_category`	No	Leader category
`player_or_team`	No	Subject

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavior — a LeagueID-only request returns 200, and 400 was seen on an earlier sampled request — but it never describes the leader-board payload, ordering, or size, and the 'echoes its whole contract' phrasing is vague. Roughly half of the text is recovery provenance rather than callable behavior.

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

Conciseness3/5

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

Two sentences plus a parenthetical, of which the 'recovered after an earlier sampled request answered 400' clause is developer provenance with no operational value to a calling agent. The genuinely useful constraint — category spelling — is buried at the end.

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?

Five optional parameters with no output schema means the description should explain more about what comes back and how player_scope/player_or_team interact, especially since player_or_team only admits 'Team'. Zero-required-parameter invocation is covered, but the return shape and scoping semantics are not.

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% and enums are already on four of five properties, so the baseline is 3. The one real addition is the category spelling note ('Points'/'Rebounds' as upstream's own form, not 'PTS'), though the schema enum already lists those exact values. Minor inconsistency: it says 'no required parameter beyond the league' when the schema declares no required parameters at all.

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 resource and scope: 'Returns the homepage leader board for one category.' That is clearly distinguishable from box-score and player-log siblings. It stops short of naming which sibling to pick instead, referencing 'leagueleaders' only to contrast parameter spellings rather than to route the agent.

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?

The only usage-adjacent statement is 'no required parameter beyond the league', which is an invocation fact, not a when-to-use rule. There is no guidance on when this homepage leader board beats nba_team_stats_leaders or the box-score family, and no exclusions are given.

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

Deploy Server