Skip to main content
Glama

LazyEdge

NFL same-game prop pairs

nfl_prop_pairs
Read-only

Same-game NFL prop pairs this week whose legs move together (a QB's passing yards with a teammate's receiving yards or catches, one receiver's catches with his yards): our chance both overs hit priced together with the correlation measured on every season since 2019, beside the two chances multiplied, and our chance and the market's on each leg. Strongest first; favoured marks a pair whose two overs we both favour at or above the market. 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_prop_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, largest edge first.
game_idNo
favoured_onlyNoOnly pairs whose two overs we both favour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, non-destructive, closed-world), and the description adds real behavioral context beyond them: the correlation is measured on every season since 2019, rows are ordered strongest-first, and the free tier restricts results to today's free game with a plan prompt for other games. It does not mention pagination or what happens when no pairs qualify.

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?

Front-loaded with the resource and its scope, and every clause carries information (correlation basis, comparison columns, ordering, free-tier limits). However, the first sentence is an overlong run-on that packs output fields into a chain of clauses, which costs some readability.

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?

For a three-parameter read-only tool with no output schema, the description does substantial work: it enumerates the returned columns, ordering, and access constraints. The remaining gap is `game_id` semantics and behavior on empty results, but nothing essential to calling it correctly is missing.

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 67%; `limit` and `favoured_only` already carry descriptions, and `game_id` is undocumented in both places (only inferable from "today's free game" and "any other game"). The description does explain what `favoured` means semantically, adding some value over the schema, but the baseline of 3 fits since the schema does most of the work.

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?

States a specific resource and scope: "Same-game NFL prop pairs this week whose legs move together", and enumerates the exact leg combinations (QB passing yards with teammate receiving yards/catches, one receiver's catches with his yards). This clearly distinguishes it from nfl_props, which returns individual props.

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?

Gives useful context for interpretation ("Strongest first", what `favoured` marks) and a concrete access prerequisite ("Without an API key: today's free game only"), but never says when to choose this over nfl_props or free_game, nor when not to use it. Usage is implied by the described output rather than stated.

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