Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_player_streak_finder

Read-only

Get 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.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the streak rows are computed upstream and emitted one per streak with identity and totals, which is useful return-shape context, but it says nothing about whether streaks are active vs historical, how minimum length defaults, or any rate/coverage caveats.

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 single substantive sentence is repeated verbatim twice, so half the description is pure waste. The content itself is compact and front-loaded once duplication and the garbled "Get Returns" opening are removed.

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?

An output schema exists, so return values need not be explained, and the annotations plus full schema coverage handle safety and parameters. What remains missing is any definition of what constitutes a "streak" and how this differs from other player stat tools, which matters for a tool an agent must select among many siblings.

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 all five optional parameters (season, league_id, min_games, player_id, season_type) are already documented in the schema. The description adds no syntax, default, or interaction detail beyond what the schema provides, so the baseline 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 names a specific verb and resource ("Returns player game streaks for a season") and clarifies the shape of the result (one row per streak, player identity and streak totals). It does not differentiate from plausible siblings like nba_player_game_logs or nba_player_dash_by_last_n_games, and the leading fragment "Get Returns" is a garbled verb phrase.

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 guidance on when to choose this tool over alternatives, no mention of prerequisites, and no exclusions. The only usage signal is the implicit "for a season" scoping, which an agent must infer.

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

All Crawlora MCP toolsInspect
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