Skip to main content
Glama

The Odds Gap

Middles

middles
Read-onlyIdempotent

Spread and total middles across sportsbooks at the scan: two numbers far enough apart that both bets could win. Its figure (ev_pct, labelled Above Break-Even) is how far the market's hit chance times the payout sits above or below what the tickets cost, not expected profit. 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": "middles"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoThe game in plain words, for example 'Lions at Bears' or 'Yankees tonight'.
pickNoA number to put in place of one side of the last middle, for 'what if I took 144.5 instead' (prompt 194).
textNoThe reader's words.
booksNoThe books this person actually has. Omit for the default set.
stakeNoThe stake on each ticket, for hit and miss dollars.

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 / pick
      Added value: +{
      +  "description": "A number to put in place of one side of the last middle, for 'what if I took 144.5 instead' (prompt 194).",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / stake
      Added value: +{
      +  "description": "The stake on each ticket, for hit and miss dollars.",
      +  "type": "number"
      +}
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the numbers are a point-in-time snapshot and 'Prices may have moved since the scan', plus a clarification that ev_pct is a breakeven margin rather than expected profit. It stops short of describing volume, pagination or what happens when no middles exist.

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?

The definition leads with what a middle is, then qualifies the headline figure, then warns about staleness — a sensible front-loaded order. The 'labelled Above Break-Even' clause and parenthetical prompt reference are slightly cluttered but each carries information.

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?

An output schema exists, so return values need not be enumerated, and the description still volunteers the meaning of the key figure (ev_pct) and the freshness caveat. For a read-only scan tool with fully documented parameters, that covers what an agent needs to call it and interpret 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 description coverage is 100%, so all five parameters are already documented, which sets the baseline at 3. The description adds only the notion of a prior scan; it does not explain how books, stake, or pick interact with the output despite those being the inputs most likely to be misused.

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?

States a specific concept ('spread and total middles across sportsbooks') and defines it concretely as two numbers far enough apart that both bets could win, which separates it from a generic odds lookup. It does not name the closest sibling (arbs) to draw the contrast, so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no alternative is named. The only contextual hook is 'at the scan' and a reference to 'prompt 194' inside a parameter description, which does not tell an agent when this tool is the right pick over arbs or game_lines.

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