proplab_gamesRetrieve NBA and WNBA games for a specific date, including teams, spreads, totals, and game status. Defaults to today's slate when no date is given.
Get NBA/WNBA games for a date: teams, spreads, totals, game status. Defaults to today.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Date in YYYY-MM-DD format. Defaults to today |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered. The description contributes the returned field set and the default-date behavior, useful context beyond the annotations, though it says nothing about game status semantics (live vs final) or data freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence that leads with the resource and scope, followed by the returned fields and default. No redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description usefully names the returned attributes, and annotations carry the safety profile for this one-optional-param read tool. Only minor details, such as what 'game status' values mean or result scope, are left unspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single 'date' parameter is already documented in the schema with format and default. The description only restates the same default, adding no new syntax or edge-case meaning, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (NBA/WNBA games for a date) and enumerates what comes back (teams, spreads, totals, game status). No sibling tool in the list offers a games-by-date listing, so an agent can route here unambiguously.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'Defaults to today' note implies when the tool applies, but there is no explicit when-to-use vs when-not guidance or reference to alternatives. Since no sibling overlaps this functionality, the gap is minor, but usage is only implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.