Skip to main content
Glama

The Odds Gap

Games on the Schedule

slate
Read-onlyIdempotent

Lists the games in a window (tonight, tomorrow, a weekday or a date) for a league or one team, with the highest moneyline price we saw on each side and the time it was scanned. Prices may have moved since the scan.

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": "slate"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoOne team: its upcoming games.
textNoThe reader's words, for the window.
whenNotoday, tonight, tomorrow, a weekday, weekend, or YYYY-MM-DD. Default the next 24 hours.
booksNoThe books this person actually has. Omit for the default set.
limitNoHow many games. Default 8, max 8.
sportNoLeague, e.g. nfl or college football.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the tool produced an answer.
cardNoThe same answer, structured, when there is one. A figure in it keeps its field name (edge_pct, ev_pct) and carries a plain label beside it: "label": "Above Fair" (percent above our fair price, not expected profit) or "Above Break-Even" for a middle.
pageYesThe matching page on theoddsgap.com.
toolNo
as_ofNoWhen the prices were scanned, Eastern Time.
staleNoTrue when that scan is older than usual for our hourly snapshot.
answerYesThe answer in plain sentences.
optionsNoWhen the question could mean more than one thing: whole questions to ask again with.
warningsNo
state_noteNoWhere to check what is legal for you.
decline_kindNoSet when the question is one we do not answer, and which kind.
free_left_todayNo
responsible_gamblingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / card / description
      Previous value: -"The same answer, structured, when there is one."New value: +"The same answer, structured, when there is one. A figure in it keeps its field name (edge_pct, ev_pct) and carries a plain label beside it: \"label\": \"Above Fair\" (percent above our fair price, not expected profit) or \"Above Break-Even\" for a middle."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent and closed-world. The description contributes something the annotations cannot: that prices are point-in-time maxima with a scan timestamp and 'may have moved since the scan', which tells the agent how stale the numbers are. It stops short of saying what happens when no games match the window.

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?

Two sentences, front-loaded with the verb and resource, then a short freshness caveat. The parenthetical window list is dense but each item maps to a real usage mode; nothing is redundant.

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 an output schema present, the return shape needn't be spelled out, and the freshness caveat plus annotations cover the main behavioral risks. The remaining gap is edge-case behavior for empty windows or an unrecognized team, which is minor for a read-only listing tool.

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 the six parameters are already documented in structured form; the description only echoes the window options and the team-vs-league choice. It adds no format or default detail beyond the schema, so the baseline 3 applies.

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 verb ('Lists') and resource ('the games') plus the scoping axes (time window, league or one team) and what each row carries (highest moneyline price per side and scan time). That is enough to separate it from a current-lines tool, though it never names a sibling explicitly.

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 window vocabulary ('tonight, tomorrow, a weekday or a date') implies when the tool is appropriate, and 'for a league or one team' implies its two modes. There is no explicit statement of when to prefer it over game_lines or past_game, so the routing is left to inference.

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