Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

betfair_markets_by_event

Retrieve market structure (IDs, names, runners) for Betfair events. Use market IDs from this tool to fetch exchange prices via betfair_market_prices.

Instructions

Market STRUCTURE for an event (market ids, names, runners) — probed live 2026-07-06: this route STRIPS exchange prices (runners come back without the exchange block) and 400s on multi-id batches. For prices, feed the market ids into betfair_market_prices; for bulk market-id discovery, betfair_navigation with attachments=MENU,EVENT,MARKET returns 1000+ MARKET nodes per event type in one call.

Returns: {currencyCode, eventTypes:[{eventNodes:[{eventId, event:{eventName}, marketNodes:[{marketId, description:{marketType}, state, runners:[{...prices}]}]}]}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_akNonzIFcwyWhrlwYMrh
altNojson
typesNoMARKET_STATE,MARKET_RATES,MARKET_DESCRIPTION,EVENT,RUNNER_DESCRIPTION,RUNNER_STATE,RUNNER_EXCHANGE_PRICES_BEST,RUNNER_METADATA,MARKET_LINE_RANGE_INFO
localeNoen
eventIdsYes
rollupLimitNo
rollupModelNoSTAKE
currencyCodeNoAUD
Behavior4/5

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

Discloses key behavioral traits: strips exchange prices, fails on multi-id batches. No annotations exist, so description carries full burden. Additional details on auth or rate limits missing, but the core behavior is well communicated.

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?

Concise and well-structured: states purpose, limitations, alternatives, then sample output. However, includes irrelevant detail ('probed live 2026-07-06') that could be omitted.

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?

Provides good high-level overview and output structure example, but fails to explain parameter usage (8 params, 1 required). Without output schema, the sample helps but does not fully compensate for missing parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain any parameter (e.g., eventIds, types, locale). Only eventIds is implied. Users get no guidance on how to set default or optional parameters.

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?

Description clearly states it returns market structure (ids, names, runners) for an event, and explicitly distinguishes from sibling tools betfair_market_prices (for prices) and betfair_navigation (for bulk discovery).

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

Usage Guidelines5/5

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

Provides explicit when-to-use: for market structure without prices. Directs to betfair_market_prices for prices and betfair_navigation for bulk market-id discovery. Also notes limitation: 400s on multi-id batches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanielTomaro13/sportsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server