Skip to main content
Glama

LazyEdge

NBA player props

nba_props
Read-only

NBA player props for today's games: the line, our projection, our chance of the over, the market's and the edge in percentage points, live once a game starts. Largest edges first. 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_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
statNo
limitNoRows to return, largest edge first.
playerNoPart of a player's name.
game_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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), so the description's job is freshness and access: it discloses that rows go live once a game starts, that results are edge-sorted, and that an unauthenticated call is limited to the free game and returns an upsell message instead of data. That last point is genuine behavioral context an agent cannot get from schema or annotations.

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?

Three short sentences, front-loaded with the returned fields, then ordering, then the access caveat - no filler. The middle clause ('the market's and the edge') is slightly elliptical and costs a re-read, but overall it is dense and well ordered.

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 it by naming the fields returned and the sort order. The auth/free-game behavior is a useful extra. The remaining gap is parameter documentation for stat and game_id, which is the one thing an agent could still get wrong.

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?

Half the parameters are undocumented in the schema (stat's enum values are not explained, game_id has no description at all) and the description does not compensate - it never mentions stat, player matching, or game_id. Only 'largest edges first' loosely echoes the limit parameter, which the schema already states, so it adds essentially no parameter meaning.

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 (NBA player props) for a specific scope (today's games) and enumerates what comes back: line, projection, over probability, market line, edge in points. That is far more specific than the title, though it never names the sibling that would be wrong to use (nba_hit_rates, nba_totals, nba_spreads) so differentiation is inferred rather than stated.

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?

Scoping to 'today's games' and 'largest edges first' implies the use case, and the no-API-key clause tells the agent what happens for non-free games. There is no explicit when-not guidance and no named alternative for historical or player-level rate questions, so an agent must infer the boundary itself.

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