Skip to main content
Glama

get_bet365_odds

Current captured bet365 prices, grouped by event: US moneyline, spread and total, and soccer match result, double chance, goal line and goalscorer prices. Each price has american, decimal and (for soccer) fractional odds, observed_at (when we read it) and age_seconds. Needs an API key.

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": {
      "user_request": "<user_request>"
    },
    "name": "get_bet365_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO time. Events starting before it.
fromNoISO time. Events starting at or after it. Default: 6 hours ago.
liveNotrue for in-play prices only, false for pre-match only.
limitNo
leagueNoLeague code, such as nba, nfl, nhl, ncaaf, ncaab, mlb, epl, serie-a, bundesliga, ligue-1 or ucl. get_bet365_coverage lists what is captured now.
marketNo
offsetNo
event_idNoAn event id from list_bet365_events, such as an-295471 or espn-401879233.
user_requestYesThe current user task in one sentence. Leave out secrets and personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose read-like behavior, data freshness (observed_at, age_seconds), price formats, and the API-key requirement. It omits pagination/limit behavior and any caching or rate-limit expectations, so some operational traits remain implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the resource and followed by return fields and auth; no filler. The dense market enumeration is justified by scope.

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?

For a 9-parameter read tool with no annotations or output schema, the description covers purpose, return fields, freshness, and auth well. It still leaves pagination (limit/offset), result ordering, and sibling selection undocumented, which are material for correct invocation.

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 coverage is 67%, and the description adds meaning mainly by mapping market names to sport contexts. It does not clarify limit, offset, user_request, or the interaction among from/to/live/league beyond the existing schema descriptions.

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 the resource (current bet365 prices), the grouping (by event), and the market set (moneyline, spread, total, and soccer markets), so an agent knows what data comes back. It does not explicitly differentiate from preview_bet365_odds or get_bet365_line_history, keeping it short of a 5.

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 when-to-use or when-not-to-use guidance and no named alternative; 'Needs an API key' is a prerequisite, not usage guidance. The market list implies the tool is for price retrieval, but an agent must infer that preview/history/coverage siblings serve different tasks.

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