Skip to main content
Glama

Line movement

get_line_movement
Read-onlyIdempotent

Use when analyzing how betting lines moved over time. Returns time-series snapshots grouped by bookmaker. Most expensive tool (25 cr). If you only need current lines, use get_odds (10 cr) instead. Prices are market information; no tool places, accepts or tracks wagers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game_id": "<game_id>"
    },
    "name": "get_line_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesNHL game ID
bookmakerNoFilter by specific bookmaker key (lowercase)

Output Schema

NameRequiredDescriptionDefault
game_idYes
movementYes
away_teamYes
home_teamYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / movement / additionalProperties / items / properties / source
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.5/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, but the description adds cost, grouped-by-bookmaker output shape, and the scope limit that no wagering is placed or tracked. Those facts are not in the annotations and materially affect planning. It stops short of pagination or volume/latency details for a 25-credit call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each with a distinct job: trigger, return shape, cost comparison plus alternative, and scope disclaimer. Front-loaded with the use case and no filler.

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?

An output schema exists, so return values need no prose, and both parameters are fully documented in the schema. Annotations plus the description cover safety, cost, and selection against the sibling, leaving nothing an agent needs in order to call it correctly.

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 100% with both parameters documented, including that bookmaker must be lowercase. The phrase 'grouped by bookmaker' hints at the filter but doesn't add syntax or default behavior beyond the schema, so the baseline of 3 is right.

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 analysis verb: 'analyzing how betting lines moved over time' and 'Returns time-series snapshots grouped by bookmaker'. That distinguishes it clearly from the current-lines sibling get_odds, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger (time-series line analysis), an explicit alternative with its cost (get_odds at 10 cr versus 25 cr here), and the condition that selects it: 'If you only need current lines'. It names the exclusion and the reason, not just the alternative.

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.