Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

betfair_markets_by_event

Read-onlyIdempotent

Retrieve market structure—market IDs, names, and runners—for a single event ID, without exchange prices. Use with betfair_market_prices for pricing.

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}]}]}]}]}

Auth: none needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_akNoPublic web app key (leave default).nzIFcwyWhrlwYMrh
altNoResponse format.json
typesNoWhich data sections to include (CSV).MARKET_STATE,MARKET_RATES,MARKET_DESCRIPTION,EVENT,RUNNER_DESCRIPTION,RUNNER_STATE,RUNNER_EXCHANGE_PRICES_BEST,RUNNER_METADATA,MARKET_LINE_RANGE_INFO
localeNoLocale.en
eventIdsYesEvent ids, e.g. 35652256 (from betfair_navigation EVENT nodes). Prefer ONE id per call — multi-id batches return 400.
rollupLimitNoPrice-ladder depth to roll up.
rollupModelNoRoll-up model.STAKE
currencyCodeNoCurrency for prices/volumes.AUD
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description reveals critical behavior: the route 'STRIPS exchange prices (runners come back without the exchange block)' and '400s on multi-id batches'. Also notes 'Auth: none needed' and provides a probed date, adding confidence and specifics.

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?

The description is front-loaded with the purpose and key limitations, followed by a concise Returns block and Auth line. Every sentence adds value: alternatives, error behavior, and response shape. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 8 params but only 1 required, the description fully covers selection and invocation: how to obtain eventIds, what to expect in the response (explicit Returns structure), and how it fits with sibling tools. The absence of an output schema is compensated by the Returns block.

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?

Schema coverage is 100%, so baseline is 3. The description enhances this by clarifying the eventIds source ('from betfair_navigation EVENT nodes') and emphasizing the one-id-per-call constraint. It also warns that despite the types default including RUNNER_EXCHANGE_PRICES_BEST, exchange prices are stripped anyway.

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?

The description clearly states the tool's purpose: 'Market STRUCTURE for an event (market ids, names, runners)'. It uses a specific verb and resource, and explicitly differentiates from siblings by directing users to 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 guidance: tells users to use this tool for market structure, not for prices (pointing to betfair_market_prices) nor for bulk discovery (pointing to betfair_navigation). Also warns against multi-id batches ('400s on multi-id batches') and advises preferring one event id per call.

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