Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_hustle_team

Retrieve NBA team hustle statistics including contested shots, deflections, charges drawn, screen assists, loose balls recovered, and box-outs by season, season type, and aggregation mode.

Instructions

Returns the league's team hustle table: contested shots, deflections, charges drawn, screen assists and points, loose balls recovered and box-outs. Returns the league's team hustle table: contested shots, deflections, charges drawn, screen assists and points, loose balls recovered and box-outs.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form; defaults to the current NBA season.
per_modeNoOptional aggregation.
league_idNoOptional league id; only 00 (NBA) is verified.
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 disclosure burden. It lists the returned metric families but says nothing about read-only semantics, pagination, error behavior for invalid seasons, or how missing data is represented. Naming the returned columns is the only behavioral contribution.

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 sentence is repeated verbatim, doubling the length with zero added information. The content itself is front-loaded and clear, but the duplication is a clear structural defect.

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 stats lookup with fully documented parameters and no output schema, the description is minimally sufficient — it conveys what data comes back. It remains incomplete on how this table differs from the player-level hustle sibling and on any behavioral caveats.

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% and every parameter (season, per_mode, league_id, season_type) carries its own description plus enums where applicable, so the schema does the heavy lifting. The description adds no filtering or formatting meaning beyond what the schema already states, which is the baseline 3 case.

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 the league's team hustle table') and enumerates the metrics covered (contested shots, deflections, charges drawn, screen assists, loose balls, box-outs). It does not differentiate itself from the sibling 'nba_hustle_stats', so an agent must infer that the distinction is team-level vs. player-level.

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 mention of the season/season_type defaults in a decision context, and no reference to any alternative tool. The agent is left to infer that this is the team-aggregate counterpart to nba_hustle_stats purely 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