Skip to main content
Glama

The Odds Gap

Arbitrage Spots

arbs
Read-onlyIdempotent

Spots where two books' prices on opposite sides of the same bet added up to less than 100 percent implied at the scan, with how a stake would split. Prices may have moved since the scan. An arb can close at any time.

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

Input Schema

NameRequiredDescriptionDefault
gameNoThe game in plain words, for example 'Lions at Bears' or 'Yankees tonight'.
textNoThe reader's words.
booksNoThe books this person actually has. Omit for the default set.
stakeNoA total stake to split.

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.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: results are snapshots taken at scan time, prices may have moved, and an arb can close at any moment. Those are the operational caveats an agent needs before presenting an arb as actionable.

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?

Three short sentences, front-loaded with the defining condition and followed by the two caveats that matter most. Nothing is redundant. The clause 'with how a stake would split' is slightly awkwardly grafted onto the definition but still earns its place.

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-shape detail is unnecessary, and the annotations cover safety. The description supplies the staleness and ephemerality warnings that the structured fields cannot. The remaining gap is scope: it never says whether results are limited to a current slate or span all games, which matters given the optional 'game' filter.

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 four parameters are already documented in the schema, which sets the baseline at 3. The description adds only one piece of parameter-adjacent meaning, that a stake split is returned, and says nothing about how 'game', 'text', or 'books' shape the scan. No compensation beyond the schema is warranted or provided.

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 gives a precise definition of the resource: spots where two books' prices on opposite sides of the same bet summed to under 100% implied, plus a stake split. That is far more specific than the name 'arbs' alone. It does not, however, contrast itself with the sibling 'middles', which is the nearest adjacent concept, so the agent must infer the boundary.

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 only implied: an agent can infer this answers questions about arbitrage opportunities. There is no explicit 'use this when' statement, no exclusion pointing to 'middles' or 'calc', and no note on whether results are scoped to a slate or date. The staleness caveat hints at when results are trustworthy but is not framed as usage 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