Skip to main content
Glama

UFC line movement

invoke_mma_line_movement
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. UFC (MMA) line movement, tracked by BankrollSZN: for each bout on the next card the opening and current moneylines, total rounds line and implied win chance per fighter (DraftKings), 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_mma_line_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
fighterNoFighter name, or part of a name.
sort_byNoDefault move (biggest change first).
include_seriesNoAdd the full price history per bout. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 context they cannot: data source (DraftKings), a 15-minute refresh cadence, UTC timestamps on history, and the notable first-call approval prompt after connection. It does not cover pagination behavior or what the plan limit does when hit, leaving a small gap for a paged tool.

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?

Content is front-loaded and every clause carries information — no filler or marketing. It is somewhat overpacked into long run-on sentences, and the approval-prompt note leads ahead of the core purpose, which slightly delays the main point.

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?

With no output schema, the description carries the return-shape burden and does it fully: fields per row, ordering, optional history expansion, and freshness. All parameters are optional and documented, so an agent has everything needed to call it correctly on the first try.

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%, so all five parameters are already documented, which sets the baseline at 3. The description does add real meaning for include_series ("adds every captured price with its time (UTC)") and confirms the default sort behavior, but it says nothing about limit, offset, or fighter beyond the schema text.

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 (UFC/MMA line movement per bout on the next card) and enumerates exactly what comes back: opening and current moneylines, total rounds line, implied win chance, change since open, sorted biggest move first. That level of specificity separates it cleanly from the odds/line-matchup siblings without needing to name them.

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 situational trigger for calling it. It stops short of naming an alternative or an exclusion (e.g. when to prefer invoke_mma_odds or invoke_mma_late_changes), so it is clear context rather than full routing guidance.

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