Skip to main content
Glama

get_bet365_line_history

How a bet365 price or line moved: one row per change, each with the interval it held (observed_at to last_seen_at). Free keys read the last 24 hours; paid plans read every change since collection began. Needs an API key. For changes pushed as they happen (alerts, live line tracking), the same key connects to the WebSocket wss://stream.thebet365api.com/v1/stream; see https://thebet365api.com/docs#websocket.

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_line_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNo
event_idNoAn event id from list_bet365_events, such as an-295471 or espn-401879233.
selection_idNoA selection_id from get_bet365_odds.
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.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full load and does substantial work: it discloses the auth requirement ('Needs an API key'), a hard result-scope limit tied to key tier, and the shape of each record (interval bounded by observed_at and last_seen_at). It does not cover error behavior or ordering, which keeps it short of a 5.

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?

Four sentences, front-loaded with the result shape before the access limits, and no filler. The closing WebSocket and docs-URL sentence is the least essential part, but it does carry a genuine alternative access path rather than repeating earlier content.

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?

For a four-parameter, no-annotation, no-output-schema tool, the description supplies most of what an agent needs: what a row is, what window of history is returned at each tier, and that an API key is required. The remaining gap is practical rather than conceptual, since nothing explains how the market/event_id/selection_id filters combine to narrow the history.

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?

At 75% schema coverage the schema already documents event_id, selection_id, and user_request, and market is constrained by an enum. The description adds no parameter-level meaning of its own, so it neither compensates for the small gap nor improves on the schema baseline.

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 opening clause gives a specific verb and resource: how a bet365 price/line moved, with 'one row per change' fixing the return granularity. It is clear on its own, but it never names get_bet365_odds or otherwise contrasts itself with the sibling that returns current prices, so the boundary is inferred rather than stated.

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?

There is real routing guidance, but it points outside the tool set: for pushed updates the description sends the agent to a WebSocket endpoint instead of this call. The tier condition ('free keys read the last 24 hours; paid plans read every change') implies when results will be incomplete, yet there is no explicit statement of when to choose this over get_bet365_odds for a snapshot.

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