Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nba_games

Fetch the current NBA game slate displayed on nba.com, including scores, status, period, clock, and team records. Use it as a no-parameter fallback to the stats-service scoreboard.

Instructions

Current NBA games from nba.com's own page state. Returns the games currently shown on nba.com's games page, read from the page's embedded JSON state: game id, code, status and clock, period, and both teams with id, tricode, name, score, wins and losses. The shape is identical to nba-scoreboard, so the two routes are interchangeable for callers. This route is an independent fallback: it uses nba.com's public website instead of the statistics service, needs no parameters, and returns the slate that page displays rather than an arbitrary date.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the data source (page-embedded JSON), that no parameters are required, that the result set is whatever the page currently shows, and that the output shape is identical to nba-scoreboard. It does not cover failure modes (page structure changes), caching/freshness lag, or rate limits, which is why it isn't a 5.

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

Conciseness4/5

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

Sentences are front-loaded with purpose first, then payload, then interchangeability, then fallback rationale – a logical order. There is mild redundancy between 'read from the page's embedded JSON state' and 'returns the slate that page displays,' but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (no params, no output schema) yet the description fully documents the return shape field by field, the data source, and its relationship to a sibling route. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no schema semantics to compensate for; baseline is 4. The description reinforces this by stating it needs no parameters and explains the implicit constraint that output is bound to whatever the page currently displays.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Current NBA games from nba.com's own page state') and enumerates the returned payload down to fields (game id, code, status and clock, period, team id/tricode/name/score/wins/losses). It also explicitly names nba-scoreboard as the equivalent route, so an agent can distinguish the two without opening a schema.

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?

It clearly frames this as an independent fallback using nba.com's public website instead of the statistics service, and notes it 'returns the slate that page displays rather than an arbitrary date' – useful guidance for when a date-filtered route is inappropriate. What's missing is an explicit when-not-to-use condition or a named parameterized alternative for historical/date-specific queries.

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

Deploy Server