Skip to main content
Glama

LazyEdge

Line moves

line_moves
Read-only

DraftKings' opening spread, total and moneyline beside its line now for each game still to start, with which way each moved relative to our number. Largest moves 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": "line_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNo

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 read-only and closed-world safety, so the description's added value is real: it discloses the data source (DraftKings), the sort order (largest moves first), the scope limit (only games still to start), and the unauthenticated fallback behavior (free game only, otherwise a plan-upsell message). It stops short of a 5 because pagination/volume limits and the exact response shape are not addressed.

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 tight sentences with the core output described first and the access constraint last; nothing is redundant. The phrasing 'beside its line now' is slightly compressed but still readable, keeping it just under a 5.

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 only one optional parameter and no output schema, the definition does the heavy lifting well by enumerating the returned fields, the ordering, the game scope, and the auth fallback. The remaining gap is the unstated default when 'sport' is not supplied, which matters 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 0% and the description never mentions the 'sport' parameter at all. The enum values (nba, nfl) are self-explanatory, but with the parameter optional and undocumented, the agent cannot tell what happens when it is omitted or whether other sports exist. The description does not compensate for the coverage gap.

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 exact resource (DraftKings opening spread, total, moneyline vs. current line for games yet to start) and the derived signal (direction of movement, sorted by magnitude). That is far more specific than the bare name 'line_moves'. It does not explicitly contrast itself with siblings like nba_spreads or nba_totals, 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 Guidelines3/5

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

The intended use is implied by 'which way each moved relative to our number' and 'Largest moves first', so an agent can infer this is for movement analysis rather than raw line lookup. However, it never states when to prefer it over nba_spreads/nba_totals, nor any exclusion or prerequisite beyond the API-key note.

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