Skip to main content
Glama

LazyEdge

NFL player props

nfl_props
Read-only

NFL player props this week where a venue lists a line: our mean and median projection, our chance of the over at the line, the market's and the edge. Largest edges first, role questions left out. 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": "nfl_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
statNo
limitNoRows to return, largest edge first.
playerNo
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 declare this is a non-destructive, non-open-world read, so the description doesn't need to restate safety. It adds real behavioral context the annotations don't cover: rows are sorted largest edge first, props without a listed line are dropped, 'role questions' are excluded, and unauthenticated callers are restricted to today's free game with a plan prompt otherwise. The one weak spot is that 'role questions left out' is unexplained jargon.

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?

Dense and front-loaded: the resource and scope come first, output fields second, sorting and exclusions third, access tier last. No filler sentences. The phrase 'role questions left out' is the one opaque fragment that doesn't earn its place without explanation.

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 usefully enumerates the returned fields, and the access-tier caveat is genuinely necessary context. But for a tool with four parameters and a stat enum, leaving stat/player/game_id semantics unaddressed leaves the definition short of complete for correct invocation.

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 description coverage is only 25% — just the limit parameter is documented. The description adds nothing about the stat enum values, how player matching works (partial name? exact?), or whether game_id narrows to a single game, even though it does clarify the limit ordering ('largest edges first') implicitly. With three of four parameters undocumented in both places, the description should be compensating and isn't.

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 names the resource (NFL player props) and pins the scope tightly: this week, only rows where a venue lists a line. It also enumerates the returned fields (mean/median projection, over probability, market line, edge), so an agent knows exactly what it gets. It stops short of naming a sibling to distinguish itself from, e.g., nfl_prop_pairs, so it lands at 4 rather than 5.

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 clearest guidance is access-tier behavior: without an API key you get today's free game only, and other games report what a plan unlocks. There is no explicit statement of when to prefer this over nfl_prop_pairs or nfl_games, so the when-to-use signal is only implied by the 'where a venue lists a line' filter.

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