Skip to main content
Glama
oddsrelay

OddsRelay

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ODDSRELAY_KEYYesYour OddsRelay API key, copied from the dashboard after signing up at app.oddsrelay.io/signup. The server reads the key only from ODDSRELAY_KEY and sends it only to https://api.oddsrelay.io.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sportsA

Lists sport and competition keys (such as soccer or soccer_epl) for the sport filter of odds and events. Costs no tokens. Paged: pass next_cursor back as cursor.

eventsA

Lists the events of one sport with their ids, for event_odds. Costs no tokens. Paged: pass next_cursor back as cursor.

bookmakersA

Lists the bookmaker and exchange keys that odds, event_odds and coverage take. Costs no tokens.

coverageA

Shows which bookmakers carry which sports on one product, and that product's market keys (the values odds takes as markets). Filter by bookmaker or sport. Costs no tokens and sends no key.

oddsA

Reads a matched board (bookmaker back prices with exchange lay prices) for one sport at the bookmakers you name. Spends tokens: priced first, and refused when it would cost more than max_tokens.

event_oddsA

Reads one event's prices (id from events or odds) at each bookmaker and exchange carrying it, narrowed to the bookmakers and markets you name. Needs a key that can read raw odds. Spends tokens: priced first, and refused when it would cost more than max_tokens.

usageA

Shows this key's plan, token balance, reset time and scope. Costs no tokens.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct aspect: discovery (sports, events, bookmakers, coverage), price retrieval (odds, event_odds), and account info (usage). Minor overlap exists between bookmakers (key list) and coverage (mapping + markets), and between odds (sport-level) and event_odds (event-level), but descriptions clarify the granularity.

Naming Consistency4/5

All tools are lowercase resource nouns (sports, events, bookmakers, coverage, odds, usage) with one snake_case compound (event_odds). Style is consistent and readable, though it deviates from a strict verb_noun pattern. Plural/singular mix is minor.

Tool Count5/5

7 tools are well-scoped for a read-only odds API: four discovery tools, two price retrieval tools, and one account tool. No redundant or missing tools at this count.

Completeness4/5

Covers the full read lifecycle: discovering sports, events, bookmakers, coverage/market keys, and fetching odds at sport and event level, plus usage. Minor gap: no dedicated tool to list market keys independently (bundled into coverage with bookmaker-sport mapping).

Maintenance

ActivityMaintained
ResponsivenessNo issues