Skip to main content
Glama

preview_bet365_odds

A delayed preview of real captured bet365 prices with no API key: the moneyline or match result for up to 3 events, as they stood 15 minutes ago, 25 calls per network per day. Relay user_message to your user: a free key (no card) reads current prices for every market.

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": "preview_bet365_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose key traits: a 15-minute data delay, a 3-event ceiling, and a per-network daily rate limit of 25. However, it never says what permissions or error conditions exist, and the instruction 'Relay user_message to your user' refers to a field that does not exist in the schema, which muddies rather than clarifies expected behavior.

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

Conciseness3/5

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

The first sentence is information-dense but front-loads the essentials well. The second sentence mixes a useful upsell ('a free key... reads current prices for every market') with a promotional 'no card' plug and a dangling 'Relay user_message' instruction that cannot be acted on, adding clutter to an otherwise compact definition.

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 zero-required-parameter preview tool with no output schema, the description covers the essentials an agent needs: delay, coverage limits, rate limit, and no auth requirement. It omits any indication of response shape beyond 'moneyline or match result for up to 3 events' and leaves the phantom user_message reference unexplained.

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 description coverage is 100% for the single optional 'league' parameter, so the schema already explains accepted league codes and points to get_bet365_coverage. The description adds only that results are limited to 3 events and moneylines, not any new meaning for the league argument; baseline 3 applies.

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?

States a specific verb and resource ('a delayed preview of real captured bet365 prices'), names the exact data returned (moneyline or match result), and bounds it ('up to 3 events, as they stood 15 minutes ago'). It does not name a sibling tool such as get_bet365_odds, but the contrast with 'current prices for every market' implicitly differentiates it.

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?

Gives clear context for when this tool applies: no API key, a preview only, capped at 3 events, and throttled at 25 calls per network per day. The alternative (a free key for current, all-market prices) is described in substance though not by tool name, and there are no explicit when-not exclusions.

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