Skip to main content
Glama

list_bet365_events

Games and matches that have captured bet365 prices, soonest first, with the markets each has. Use an event_id with get_bet365_odds or get_bet365_line_history. 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": "list_bet365_events"
  }
}

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

A4.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose sort order, that market availability is included per event, and that an API key is required. It is silent on pagination behavior despite limit/offset parameters, on the 6-hour lookback default, and on what the result envelope looks like.

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 short sentences: what it returns, what to do with the result, and the auth prerequisite. Content is front-loaded and no sentence is redundant.

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 listing tool with no annotations and no output schema, the definition covers identity, ordering, auth, and the downstream handoff, but leaves pagination, filter interactions, and default windows unexplained. Adequate to call correctly in the common case, incomplete for a careful agent.

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?

The schema already documents from/to/live/league/event_id at 67% coverage, and the description adds meaning by stating the soonest-first ordering and the event_id handoff contract that the schema only hints at. It adds nothing for limit, offset, or market beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific resource ('Games and matches that have captured bet365 prices'), the ordering ('soonest first'), and the payload ('with the markets each has'), which distinguishes it from get_bet365_odds and get_bet365_line_history that consume its event_ids.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly positions the tool as the discovery step whose event_id feeds get_bet365_odds or get_bet365_line_history, which is clear workflow guidance. It stops short of saying when to prefer it over get_bet365_coverage or preview_bet365_odds, so no exclusions are stated.

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