Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_player_streak_finder

Find NBA player game streaks for a season and return one row per streak with player identity and streak totals; filter by player, season type, or minimum games.

Instructions

Returns player game streaks for a season: the streak rows the upstream computes, one row per streak, with the player identity and streak totals. Returns player game streaks for a season: the streak rows the upstream computes, one row per streak, with the player identity and streak totals.

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_player_streak_finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form; defaults to the current NBA season.
league_idNoOptional league id; only 00 (NBA) is verified.
min_gamesNoOptional minimum streak length in games.
player_idNoOptional player id from nba-players; narrows the streaks to one player.
season_typeNoOptional season type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one useful trait, that the streak rows are 'the upstream computes' rather than derived by this tool, but it says nothing about ordering, row caps, how streaks are counted, whether results are season-wide or require player_id, or any auth/rate-limit characteristics for a 5-parameter tool.

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

Conciseness2/5

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

The entire two-sentence description is repeated verbatim, doubling the length without adding a single new fact. The content that is there is front-loaded and readable, but the duplication is pure waste and inflates the definition for no informational gain.

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 read-only list tool with fully covered schema and no output schema, the definition is minimally sufficient: an agent knows what comes back (streak rows with player identity and totals). It is incomplete in that nothing tells the agent when this tool is the right choice among the many player-stat siblings, and the upstream-computed caveat is not unpacked.

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 every parameter including season, league_id, min_games, player_id, and season_type is already documented, which sets the baseline at 3. The description adds only the loose framing 'for a season' and does not explain how min_games interacts with streak length or what happens when player_id is omitted.

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 names a specific verb and resource ('Returns player game streaks for a season') and pins down the grain: one row per streak, with player identity and streak totals. It does not distinguish this from plausible siblings such as nba_player_game_logs, which could equally be read as per-game player data, so it stops short of the top score.

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 when-to-use guidance, no exclusions, and no named alternative. The description never says whether to reach for this instead of a game-log or season-totals tool when the user asks about consistency or hot streaks, leaving the routing decision entirely to inference from the name.

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