Skip to main content
Glama

The Odds Gap

How The Odds Gap Works

site_info
Read-onlyIdempotent

Explains a betting term or how The Odds Gap works (gap percent, matched lines, the exchange depth rule, Kalshi fees, why offshore books are left out, the site's tools), in the site's own words with a link to the page it comes from.

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": {
      "text": "<text>"
    },
    "name": "site_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reader's words.
topicNoA topic key, or omit to read the words.

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description does add useful return context: answers are given 'in the site's own words with a link to the page it comes from', telling the agent the response is sourced and citable. It stops short of describing fallback behavior when a term is not found or how the answer is matched.

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?

Purpose is front-loaded in the first clause and the parenthetical topic list is efficient enumeration rather than padding. The single sentence is somewhat long and the nested parenthetical could be trimmed, but every element conveys scope the agent can use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be spelled out, and the safety annotations cover behavior, so the description is close to adequate for a simple two-parameter lookup. The remaining gap is the text-vs-topic mechanics and what happens on a miss, which an agent would need to know to call 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 the baseline is 3 and the schema carries the burden. The description adds no information about how 'text' (the reader's words) and the optional 'topic' key interact — notably whether supplying a topic bypasses free-text matching — even though the schema's own one-line descriptions ('A topic key, or omit to read the words') are terse enough to leave that relationship ambiguous.

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 verb and resource: it explains a betting term or how The Odds Gap works, and enumerates the topic areas (gap percent, matched lines, exchange depth rule, Kalshi fees, offshore books, site tools). That is far more concrete than a generic 'get info' tool and implicitly separates it from the numeric siblings like futures_odds and arbs, though it never names an alternative.

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 by the phrasing 'Explains a betting term or how The Odds Gap works' — an agent can infer it is for conceptual/definitional questions rather than odds lookups. There is no explicit when-to-use trigger, no when-not-to-use case, and no mention of the sibling tools that handle the actual data.

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