Skip to main content
Glama

The Odds Gap

Futures Prices

futures_odds
Read-onlyIdempotent

Season-long futures such as the Super Bowl, World Series, Stanley Cup, NBA and college titles: the highest price we saw on a team, or the top of one futures market, with the scan time. 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": "futures_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoOne entrant, if they named one.
textNoThe person's own words. This is what names the market, because a futures market has no id anybody would ever say out loud.
booksNoThe books this person actually has. Omit for the default set.
sportNoThe league, if no market is named.
stakeNoA stake to pay out at the best price.
teamsNoTwo or more entrants asked together.
marketNoA market phrase, if it is separable from the rest of the sentence.
compareNoBooks the person named, to say each one's price.

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. Changed4 schema fields changed
    • addedInput schema / properties / compare
      Added value: +{
      +  "description": "Books the person named, to say each one's price.",
      +  "type": "array"
      +}
    • addedInput schema / properties / sport
      Added value: +{
      +  "description": "The league, if no market is named.",
      +  "type": "string"
      +}
    • addedInput schema / properties / stake
      Added value: +{
      +  "description": "A stake to pay out at the best price.",
      +  "type": "number"
      +}
    • addedInput schema / properties / teams
      Added value: +{
      +  "description": "Two or more entrants asked together.",
      +  "type": "array"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description earns credit for disclosing the staleness caveat ('Prices may have moved since the scan') and that prices are the best observed rather than a live quote, but says nothing about coverage breadth, refresh cadence, or what happens when no market matches.

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?

Two sentences, front-loaded with the substantive scope and followed by the freshness caveat; nothing is filler. The phrasing around 'the top of one futures market' is slightly compressed and takes a second read, which keeps it off a 5.

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?

Eight optional parameters and an existing output schema mean the description does not need to document return shape, and the freshness caveat and price definition are the key behavioral facts an agent needs. It stops short of explaining free-text interpretation strategy or behavior with empty results, but is adequate for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already carries parameter meaning and a baseline of 3 applies. The description adds a little framing by explaining that free text is what names the market (futures markets have no speakable id) and that a team-level best price is the returned unit, which helps an agent compose the text parameter rather than guessing a market identifier.

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 concrete domain (season-long futures: Super Bowl, World Series, Stanley Cup, NBA and college titles) and states exactly what is returned — the highest price seen on a team or the top of a single futures market, with scan time. That is specific enough for an agent to tell this apart from game_lines or player_prop, though no sibling is named 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?

Usage is implied by 'season-long futures' and the market examples, and the parameter notes ('if they named one', 'if it is separable') hint at call shapes. There is no explicit statement of when to choose this over arbs, middles, or game_lines, and no exclusions or prerequisites, so guidance is implicit only.

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