Skip to main content
Glama

NBA player props vs projections

invoke_nba_props
Read-onlyIdempotent

NBA player prop lines for the next slate: points, rebounds, assists, threes, steals and blocks. One main line per player and market (the line closest to even odds), over and under American odds, the no-vig over probability, and the BankrollSZN projection for that stat with the gap to the line (bsz_minus_line, positive means the projection is over the line) and projected minutes. Lines refresh every 20 minutes during the day.

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": "invoke_nba_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation, for example NY or OKC.
limitNoMaximum rows to return. The plan limit applies on top.
marketNoOnly this market.
playerNoPlayer name, or part of a name.
playersNoUp to 15 player names. Returns the props of every named player in one call. Use this instead of one call per player. (maxItems: 15)
sort_byNoedge sorts by the absolute gap between projection and line. Default edge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / market / enum
      Previous value: -[
      -  "points",
      -  "rebounds",
      -  "assists",
      -  "threes",
      -  "steals",
      -  "blocks"
      -]New value: +[
      +  "points",
      +  "rebounds",
      +  "assists",
      +  "threes",
      +  "steals",
      +  "blocks",
      +  "pra",
      +  "pts_reb",
      +  "pts_ast",
      +  "reb_ast",
      +  "stl_blk"
      +]
    • addedInput schema / properties / players
      Added value: +{
      +  "description": "Up to 15 player names. Returns the props of every named player in one call. Use this instead of one call per player. (maxItems: 15)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: only one main line per player and market (closest to even odds), the refresh cadence of every 20 minutes, and the sign convention for bsz_minus_line. It does not mention result-set size, truncation, or the plan limit, which the schema partially covers.

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 sentences, front-loaded with the resource and market list, followed by row semantics and then freshness. Every clause carries information (selection rule, odds format, derived fields, refresh interval) with no filler. Slightly dense with parentheticals, but nothing is redundant.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe return values, and it does: line, over/under American odds, no-vig over probability, projection, gap-to-line with sign meaning, and projected minutes. Combined with annotations covering the safety profile and a fully documented input schema, an agent has everything needed to call and interpret this tool.

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 100%, including enum meanings and the 'edge' default for sort_by, so the schema does the heavy lifting and baseline 3 applies. The description adds no parameter-level detail such as accepted team abbreviation format or the interaction between limit and the plan limit. Its explanatory effort is spent on return fields rather than inputs.

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 opens with a specific resource and scope: 'NBA player prop lines for the next slate', then enumerates the six markets covered. An agent immediately knows this returns betting lines, not raw projections or a player index. It stops short of naming how it differs from invoke_nba_projections, so sibling differentiation is only implicit.

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 content ('lines for the next slate'), so an agent can infer this is the tool for current prop lines. However, there is no explicit when-to-use statement, no exclusion, and no routing advice versus invoke_nba_projections or invoke_nfl_props/invoke_mlb_props. The one piece of routing advice ('use this instead of one call per player') lives in the schema for the players param, not in the description.

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