Skip to main content
Glama

Lumify Sports Intelligence

by ai.lumify
OverviewDiscussionsAdmin

grade_slip

Read-onlyIdempotent

Grade settleable player-prop legs (over / under / push / in_progress / dnp / no_stat) for nfl, nba, ncaaf, ncaab, nhl, mlb, and soccer — the same sport coverage as get_player_props — plus structured game markets (h2h / spreads / totals) on any sport get_odds already settles. Prefer structured event_id + market_key + side; player_id and line are required on props, line is required on spreads/totals, and both player_id and line are omitted on h2h. team_total requires team_id + line + over/under and is only gradable on nfl/ncaaf/mlb/soccer. draw is only gradable on soccer h2h — off soccer it comes back unmapped. Free-text game phrases (Chiefs -3.5, Over 47.5 vs Bills, Yankees ML, Yankees to win, Yankees over 4.5 runs, Over 52.5 Syracuse vs Pittsburgh, Novak Djokovic ML) grade when the team or player and event resolve uniquely — Over 47.5 alone stays unmapped and is never the first slate game. A tennis moneyline leftover is a player, not a team; vs is the opponent player. Last-name-only tennis stays unmapped. A last-name-only player prop (Bergeron over 1.5 shots on goal last night) grades when a date is present and that surname is unique in scope — a named sport, team, or event narrows it (Johnson nhl last night); with no such clue, uniqueness is across every prop sport the key can see. No date, or a surname shared by more than one player in that scope, stays unmapped unless a date is present and exactly one of those candidates played in the window (optionally vs a named opponent). A colliding team nickname plus a date promotes only the unique in-window club; a football-sized line will not pick a baseball club. anytime goal / anytime assist (soccer_goals/soccer_assists over 0.5) and over a hit / over a homer (hits/home_runs over 1.0) need no explicit number. Free-text player props are graded only when player and event resolve uniquely — never guesses an ambiguous name. A roster-team mention (CIN, Niners) is resolved first; unique team_id scopes the player, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent and narrows the event, not the player's team. Ambiguous events stay on event_resolve with candidates. Read legs[].result / current / market for the grade; use resolve.player_id to re-issue structured props. Call this tool with an API key to grade from an agent. Capped at 3 concurrent calls per key (shared with POST /v1/grade/slip). The public /grade sheet uses the same engine without a key (20 grades / IP / day). How-to: https://lumify.ai/docs/grade. Not live trading odds. Not wagering advice. Attribution is always Graded by Lumify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
legsNo
textNoFree-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML / Yankees to win / Yankees over 4.5 runs / Over 52.5 Syracuse vs Pittsburgh / Novak Djokovic ML / Mbappe anytime goal / Judge over a hit / Bergeron over 1.5 shots on goal last night). Date words (today, tonight, yesterday, last night, last Wednesday, this Thursday, or an ISO date) narrow the event. A roster-team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent, not the player's team. A tennis moneyline leftover is a player; vs is the opponent player. "anytime goal"/"anytime assist" implies soccer_goals/soccer_assists over 0.5 with no explicit number; "over a hit"/"over a homer" implies hits/home_runs over 1.0. A last-name-only player prop grades when a date is present and the surname is unique in scope (a named sport, team, or event narrows it; otherwise every visible prop sport); no date, or a shared surname in that scope, still refuses. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped.
cluesNoOptional sport / league / event_id / team_id / team_text hints for free-text mode.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
legsNo
statusNograded | partial | pending | unmapped
honestyNo
slip_idNo
summaryNo
brandingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML / Yankees to win / Yankees over 4.5 runs / Novak Djokovic ML / Mbappe anytime goal / Judge over a hit / Bergeron over 1.5 shots on goal last night). Date words (today, tonight, yesterday, last night, last Wednesday, this Thursday, or an ISO date) narrow the event. A roster-team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent, not the player's team. A tennis moneyline leftover is a player; vs is the opponent player. \"anytime goal\"/\"anytime assist\" implies soccer_goals/soccer_assists over 0.5 with no explicit number; \"over a hit\"/\"over a homer\" implies hits/home_runs over 1.0. A last-name-only player prop grades when a date is present and the surname is unique in scope (a named sport, team, or event narrows it; otherwise every visible prop sport); no date, or a shared surname in that scope, still refuses. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."New value: +"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML / Yankees to win / Yankees over 4.5 runs / Over 52.5 Syracuse vs Pittsburgh / Novak Djokovic ML / Mbappe anytime goal / Judge over a hit / Bergeron over 1.5 shots on goal last night). Date words (today, tonight, yesterday, last night, last Wednesday, this Thursday, or an ISO date) narrow the event. A roster-team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent, not the player's team. A tennis moneyline leftover is a player; vs is the opponent player. \"anytime goal\"/\"anytime assist\" implies soccer_goals/soccer_assists over 0.5 with no explicit number; \"over a hit\"/\"over a homer\" implies hits/home_runs over 1.0. A last-name-only player prop grades when a date is present and the surname is unique in scope (a named sport, team, or event narrows it; otherwise every visible prop sport); no date, or a shared surname in that scope, still refuses. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."
  2. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML / Yankees to win / Yankees over 4.5 runs / Novak Djokovic ML / Mbappe anytime goal / Judge over a hit / Bergeron over 1.5 shots on goal last night). Date words (today, tonight, yesterday, last night, last Wednesday, or an ISO date) narrow the event. A roster-team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent, not the player's team. A tennis moneyline leftover is a player; vs is the opponent player. \"anytime goal\"/\"anytime assist\" implies soccer_goals/soccer_assists over 0.5 with no explicit number; \"over a hit\"/\"over a homer\" implies hits/home_runs over 1.0. A last-name-only player prop grades when a date is present and the surname is unique in scope (a named sport, team, or event narrows it; otherwise every visible prop sport); no date, or a shared surname in that scope, still refuses. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."New value: +"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML / Yankees to win / Yankees over 4.5 runs / Novak Djokovic ML / Mbappe anytime goal / Judge over a hit / Bergeron over 1.5 shots on goal last night). Date words (today, tonight, yesterday, last night, last Wednesday, this Thursday, or an ISO date) narrow the event. A roster-team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent, not the player's team. A tennis moneyline leftover is a player; vs is the opponent player. \"anytime goal\"/\"anytime assist\" implies soccer_goals/soccer_assists over 0.5 with no explicit number; \"over a hit\"/\"over a homer\" implies hits/home_runs over 1.0. A last-name-only player prop grades when a date is present and the surname is unique in scope (a named sport, team, or event narrows it; otherwise every visible prop sport); no date, or a shared surname in that scope, still refuses. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."
  3. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML). Date words (today, tonight, yesterday, last night, last Wednesday, or an ISO date) narrow the event. A team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."New value: +"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML / Yankees to win / Yankees over 4.5 runs / Novak Djokovic ML / Mbappe anytime goal / Judge over a hit / Bergeron over 1.5 shots on goal last night). Date words (today, tonight, yesterday, last night, last Wednesday, or an ISO date) narrow the event. A roster-team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. vs/at on a player prop is the opponent, not the player's team. A tennis moneyline leftover is a player; vs is the opponent player. \"anytime goal\"/\"anytime assist\" implies soccer_goals/soccer_assists over 0.5 with no explicit number; \"over a hit\"/\"over a homer\" implies hits/home_runs over 1.0. A last-name-only player prop grades when a date is present and the surname is unique in scope (a named sport, team, or event narrows it; otherwise every visible prop sport); no date, or a shared surname in that scope, still refuses. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."
  4. Changed8 schema fields changed
    • addedInput schema / properties / legs / items / properties / line / description
      Added value: +"Required on props, spreads, totals, and team_total. Omit on h2h. Signed to the submitted side, not the favorite — side=home with a home -3.5 favorite is line=-3.5."
    • changedInput schema / properties / legs / items / properties / market_key / description
      Previous value: -"e.g. receiving_yards. Aliases such as player_reception_yds are accepted."New value: +"Player-prop slug (e.g. receiving_yards), game market h2h | spreads | totals, or team_total. Aliases accepted: player_reception_yds -> receiving_yards, moneyline/ml -> h2h, spread -> spreads, total/ou -> totals, team totals/tt -> team_total."
    • addedInput schema / properties / legs / items / properties / player_id / description
      Added value: +"Required on player-prop markets. Forbidden on h2h, spreads, totals, and team_total."
    • changedInput schema / properties / legs / items / properties / side / description
      Previous value: -"over or under"New value: +"Props and totals: over | under (o | u also accepted). Spreads: home | away, matching the signed line above. Moneyline: home | away, or draw on soccer only."
    • addedInput schema / properties / legs / items / properties / side / enum
      Added value: +[
+  "home",
+  "away",
+  "over",
+  "under",
+  "draw"
+]
    • addedInput schema / properties / legs / items / properties / team_id
      Added value: +{
+  "description": "Required on team_total. Forbidden on player-prop, h2h, spreads, and totals.",
+  "type": "integer"
+}
    • changedInput schema / properties / legs / items / required
      Previous value: -[
-  "event_id",
-  "player_id",
-  "market_key",
-  "line",
-  "side"
-]New value: +[
+  "event_id",
+  "market_key",
+  "side"
+]
    • changedInput schema / properties / text / description
      Previous value: -"Free-text slip (e.g. Chase over 74.5 receiving yards tonight). Date words (today, tonight, yesterday, last night, last Wednesday, or an ISO date) narrow the event. A team span is resolved first; unique team_id scopes the player, and ambiguous/not_found stays on team_resolve. Graded only when player and event are unique."New value: +"Free-text slip (e.g. Chase over 74.5 receiving yards tonight, or Chiefs -3.5 / Over 47.5 vs Bills / Yankees ML). Date words (today, tonight, yesterday, last night, last Wednesday, or an ISO date) narrow the event. A team span is resolved first; unique team_id scopes a player or binds a game/team-total leg, and ambiguous/not_found stays on team_resolve. Graded only when team/player and event are unique. A bare Over 47.5 stays unmapped."
  5. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Free-text slip (e.g. Chase over 74.5 receiving yards). A team span is resolved first; unique team_id scopes the player, and ambiguous/not_found stays on team_resolve. Graded only when player and event are unique."New value: +"Free-text slip (e.g. Chase over 74.5 receiving yards tonight). Date words (today, tonight, yesterday, last night, last Wednesday, or an ISO date) narrow the event. A team span is resolved first; unique team_id scopes the player, and ambiguous/not_found stays on team_resolve. Graded only when player and event are unique."
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare the tool read-only and idempotent, and the description adds substantial operational context: rate limits ('Capped at 3 concurrent calls per key'), public-sheet quotas ('20 grades / IP / day'), 'Not live trading odds', attribution behavior, and where to read results via legs[].result / current / market. There is no contradiction with the annotations.

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?

The description is long but front-loaded and dense, moving from core purpose to structured usage to free-text edge cases to operational caveats. Every sentence contributes a distinct rule or constraint; there is no filler or repetition that weakens it.

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?

The description covers structured and free-text inputs, disambiguation rules, failure modes, rate limits, authentication context, output location, and documentation links. With an output schema already present, the absence of explicit return-value detail is acceptable.

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

Parameters5/5

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

Even with 67% schema coverage, the description adds decisive parameter context: line is signed to the submitted side, player_id and line are required on props, line is required on spreads/totals, both are omitted on h2h, team_total requires team_id and line, and draw is only gradable on soccer h2h. This goes well beyond the raw schema.

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?

The description opens with a specific verb and resource: 'Grade settleable player-prop legs' and 'structured game markets'. It also distinguishes the tool from siblings by explicitly referencing get_player_props and get_odds for sport-coverage comparison.

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?

The description clearly advises preferring structured event_id + market_key + side and explains when free-text grading succeeds or stays unmapped. It names sibling tools for coverage context but does not give an explicit 'use X instead when...' exclusion, so it stops just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lumify Sports Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources