Skip to main content
Glama

LazyEdge

NBA games today

nba_games
Read-only

Every NBA game today, before the tip and in play: the team our number has winning (pick) and our chance (pick_p), what our pregame picks at that chance have won this season, the market price on our pick, the edge, the score and the clock. Without an API key: today's free game only; any other game says what a plan unlocks.

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

NameRequiredDescriptionDefault
live_onlyNoOnly games in play.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavior the annotations do not: pregame vs live coverage, the exact contents of each row, and the API-key gating that changes what a caller actually receives. It stops short of describing rate limits, freshness/latency of the live score, or empty-result behavior.

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?

A single dense sentence, front-loaded with the scope, followed by the payload contents and the access caveat. Given there is no output schema, every clause earns its place by telling the agent what will come back.

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

Completeness4/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 carries the return-value burden and does so by enumerating the fields, plus it discloses the free-tier behavior that shapes the response. It loses a point for unexplained internal jargon ('our number', 'pick_p') that an agent cannot decode from the definition alone.

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 coverage is 100% and the single parameter (live_only) is documented in the schema itself. The description's phrase 'before the tip and in play' gestures at the pregame/live distinction but never explicitly links it to live_only, so the schema still does the work here.

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 names the resource and scope precisely (every NBA game today, pregame and in play) and enumerates the returned values (pick, pick_p, season record, market price, edge, score, clock). That is enough to distinguish it from nba_spreads, nba_totals, nba_props and nfl_games without opening any schema.

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?

Usage is implied by the title and scope ('today's games'), and the description usefully explains the access tier: free users get today's free game only, other games return an upsell message. However, it never states when to choose this over sibling tools such as nba_spreads or nba_props, and never mentions exclusions or prerequisites.

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