Skip to main content
Glama

Historical NBA event games

get_events_catalog
Read-onlyIdempotent

Validated historical basketball context games for one NBA season. Mandatory season YYYY-YY; catalog reports loaded game/event counts and provenance. These are not historical Underdog lines.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league": "<league>",
      "season": "<season>"
    },
    "name": "get_events_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
leagueYesNBA
seasonYesFile year 2025 is season 2024-25. Current season archives are explicitly partial.
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds meaningful context beyond that: the data is validated, scoped to a single season, reports counts plus provenance, and does not contain betting lines. It does not discuss pagination behavior or the partial-archive caveat beyond echoing the schema, which keeps it short of 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.

Conciseness5/5

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

Three short sentences, front-loaded with the resource and scope, then the requirement, then the disambiguation. Every sentence carries information and nothing is repeated.

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?

With no output schema, the description does its part by saying the catalog returns game/event counts and provenance, so an agent knows roughly what comes back. However, for a five-parameter paginated tool it says nothing about cursor/limit behavior or how to interpret partial-season archives, leaving gaps an agent must discover by calling.

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 40%, and the description only reinforces the season parameter ('Mandatory season YYYY-YY'), which the schema already specifies with a pattern. It adds no meaning for league, limit, cursor, or user_request, though those are largely self-explanatory from their schema definitions and defaults.

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 the resource (historical basketball event games / catalog) and its scope (one NBA season), and explicitly bounds it with 'these are not historical Underdog lines.' The verb is only implied ('catalog reports'), so it is slightly less crisp than a verb+resource statement, but an agent can tell this is a season-scoped coverage/counts endpoint rather than a per-event data pull.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the mandatory season prerequisite and what the catalog reports (loaded game/event counts and provenance), which implies the use case: inspect what data is available for a season. It gives no explicit when-to-use versus alternatives such as get_events or get_coverage, and no when-not-to-use guidance, so usage must be inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources