Skip to main content
Glama

NFL line movement

invoke_nfl_line_movement
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. NFL line movement, tracked by BankrollSZN: for each upcoming game the opening and current moneylines, spread, total and team implied points (FanDuel), the change since open and the biggest move first. include_series true adds every captured price with its time (UTC). Use it to see where the market moved before you build or bet. Refreshes every 15 minutes from the BankrollSZN line movement board.

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_nfl_line_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation, home or away.
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
sort_byNoDefault move (biggest change first).
include_seriesNoAdd the full price history per game. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: a first-call approval prompt, a 15-minute refresh cadence from the BankrollSZN board, and confirmation that plan limits stack on top of the limit parameter. It does not state response volume, error behavior, or what happens when approval is denied, leaving some gaps.

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?

Roughly 90 words is appropriate for a 5-parameter data tool with no output schema, and the approval caveat plus the data contents are front-loaded. The long enumerative middle sentence is a run-on, and the approval note reads as an odd preamble, but there is little pure filler.

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 so by listing source (FanDuel), fields, ordering, and the series option with UTC timestamps. Freshness, billing/plan caveats, and the one-time approval are covered; only edge behavior (empty results, approval failure) is unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: include_series true returns "every captured price with its time (UTC)", and the default ordering is biggest move first. It says nothing about the team or offset parameters beyond what the schema already documents.

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 a specific resource (upcoming NFL games' opening and current moneylines, spread, total, team implied points) and enumerates the exact contents plus ordering (biggest move first), so an agent knows precisely what it retrieves. It does not explicitly contrast itself with the nearest sibling, invoke_nfl_line_matchups, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it to see where the market moved before you build or bet" gives a clear use context tied to a downstream task. There are no explicit exclusions or named alternatives (e.g. when to prefer matchups or props instead), so it lacks the routing language that would earn a 5.

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