Skip to main content
Glama

LazyEdge

NBA totals

nba_totals
Read-only

Each NBA game's total today: the market's line and price beside our projected total, pregame and live. 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_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam code, such as NY, LAL or BOS.
game_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 response pairs market line/price with a model projection and covers both pregame and live states. It also discloses a genuine access constraint — without a key only today's free game is available, and other games return a message describing what a plan unlocks rather than data.

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?

Two sentences, front-loaded with what the tool returns, then the access caveat. Dense and wasteful-free, though 'says what a plan unlocks' is slightly loose phrasing for what is presumably an error/upsell payload.

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 a reasonable job of characterizing the return shape and the free-tier behavior. The gap is parameters: for a two-param filter tool with zero required fields, the description should clarify that calling with no arguments returns all of today's games.

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

Parameters2/5

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

Schema coverage is only 50% — team is documented, game_id is not — and the description says nothing about either parameter. It never explains whether team and game_id are optional filters, what omitting both returns, or how team codes relate to game_id, so the agent must guess at call semantics.

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?

States a specific resource and payload: each NBA game's total, pairing the market line and price with a projected total, pregame and live. That is concrete enough to distinguish it from a spreads or props tool, though it never names a sibling to contrast with.

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?

The 'today' scope and the pregame/live split imply when the data is relevant, and the API-key clause tells the agent what happens on a free tier. It does not say when to pick this over nba_spreads or nba_props, which is the main routing question for a totals tool.

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