Skip to main content
Glama

The Odds Gap

Game Lines

game_lines
Read-onlyIdempotent

One game's moneyline, spread or total: both sides on the consensus number, or which side the market has as the favorite. Name the game in plain words, for example Lions at Bears. Shows the scan time and a link to the game's page. Prices may have moved since the scan.

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": "<game>"
    },
    "name": "game_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesThe game in plain words, for example 'Lions at Bears' or 'Yankees tonight'.
lineNoThe spread or total the bet is at. Omit for a moneyline, or to use the consensus line.
sideNohome or away for a moneyline or spread; over or under for a total.
teamNoA known team with no game on the board.
booksNoThe books this person actually has. Omit for the default set.
marketNoml, spread or total.
favoredNoWho the market favors, as a price.
marketsNoGame-line markets to show, both sides each.

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. Changed1 schema field changed
    • addedInput schema / properties / markets
      Added value: +{
      +  "description": "Game-line markets to show, both sides each.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / team
      Added value: +{
      +  "description": "A known team with no game on the board.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower, and the description still adds real value: it discloses that results carry a scan time, include a link to the game page, and that prices may have moved since the scan. That staleness caveat is exactly the kind of operational context annotations can't express.

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?

Four short sentences, front-loaded with what the tool returns, followed by the input convention and the caveat. Nothing is padded, though the game-naming example partially duplicates the schema's own example.

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 a full output schema, return values need no explanation, and the description covers purpose, input convention, and data-freshness risk. The one gap is the interplay among the eight parameters (e.g., when to use favored versus side plus line), which is left to the schema.

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 description coverage is 100%, so the baseline is 3 regardless of what the description adds. The description restates the 'plain words' game parameter with an example already present in the schema, and gestures at the consensus-versus-favored distinction, but does not clarify the roles of line, side, books, market, favored, or markets. It neither compensates for nor undermines the schema.

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 and its scope: 'One game's moneyline, spread or total,' which separates it from multi-game views like slate or futures. It clearly states the returned content (both sides on the consensus number, or the favored side). It stops short of naming a sibling tool to contrast against, so it's clear but not maximally differentiated.

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?

Usage is implied rather than stated: 'Name the game in plain words' tells the agent how to supply the required argument, which signals a single-game lookup. There is no explicit when-to-use versus when-to-use-something-else guidance, and no exclusions or prerequisites are given.

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