Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

sportsbet_price_slip

Read-onlyIdempotent

Get the authoritative current price for a bet slip before placing a bet. Use this price to place a real bet, as placement accepts only a price you assert.

Instructions

PRICE A BET SLIP — the authoritative, current price for selections you are about to back. Call this IMMEDIATELY before sportsbet_place_bet: placement takes a price you assert, not a quote id, so this is the only way to place at a real number.

Returns: {betBuilds:[{betNo, enhancedOdds:[{outcome, priceDecimal, priceNum, priceDen, legType}], betCombinations:[{betType, betTypeName, betMinStake, betNoOfLines, cashoutAvailable, betEnhancedPrice}], vouchers:[]}]} — VERIFIED live 2026-08-27.

THIS IS THE AUTHORITATIVE PRICE, and it is the call to make immediately before placing. sportsbet_place_bet does NOT take a quote id: it takes a price you assert, so the only way to place at a real price is to read it here first and send THAT number. A price remembered from thirty seconds ago is not a price.

betMinStake comes back per combination and was 0.01 on the verified slip — the smallest possible test bet is a cent, not a dollar.

Prices appear twice and in two forms: priceDecimal on each enhanced odd, and priceNum/priceDen which is what placement wants. Carry the fraction across unchanged rather than re-deriving it from the decimal, which rounds.

Auth: works without a key; SPORTSBET_REFRESH_TOKEN unlocks more if set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoClient channel. `cxp` is what the website sends; leave it.cxp
appTokenYesSportsbet's app key — a short constant the web client sends on every /apigw call. Not a personal credential, but not published either; read it from the browser once. Collected by `sportsdata-mcp connect sportsbet`.
betItemsYesThe slip: [{"betNo": 1, "legs": [{...}]}]. Leg shape matches sportsbet_place_bet — see its description for the parts/externalId structure.
requestIdNoA fresh UUID per call, for Sportsbet's own tracing. Optional here; send a new one each time if you send one at all.
apiVersionNoPricing is served at 2.0.0 (placement is 3.0.0). Understating it silently gets you an older schema.2.0.0
customerIdYesYour own account number. It is also the `custId` claim inside the access token, so it is not extra authority — the gateway just wants it stated. Collected by `connect`.
includeMBSNoInclude minimum bet size information.
outcomeGroupsNoREQUIRED even when empty — omitting it is refused 'Field is required: outcomeGroups'. The declared default now actually reaches the wire (see registry._value_for); before that fix a `default: []` on a body param was decorative.
returnVouchersNoInclude vouchers.
returnFreebetTokensNoInclude eligible freebet tokens.
returnOutcomeDetailsNoInclude the outcome detail; useful for confirming you priced what you meant.
returnCashoutAvailableNoWhether cash-out is offered on the resulting bet.
Install Server

TDQS

A4.4/5.0
Behavior5/5

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

Despite readOnly/openWorld/idempotent annotations, the description adds substantial behavioral context: placement has no quote id, prices must be read fresh, the fraction should be carried rather than re-derived, betMinStake was verified at 0.01, and auth works without a key. This goes well beyond what the annotations already communicate and matches them, with no contradiction.

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?

The description is dense and front-loaded, with the core purpose and critical placement warning at the top. It is longer than minimal, and some points like 'no quote id' and 'authoritative price' are repeated, but nearly every sentence carries operational value.

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?

There is no output schema, so the description carries the burden of explaining the return shape, and it does so with a concrete verified structure, including betBuilds, enhancedOdds, betCombinations, and vouchers. It also covers the minimum stake, price formatting, auth behavior, and the critical relationship to sportsbet_place_bet, making it complete for correct invocation.

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?

The input schema has 100% description coverage, so the baseline is 3. The main description adds some auth and output semantics, but it does not add much parameter-level meaning beyond what the schema already provides; the schema property descriptions already cover appToken, betItems, outcomeGroups, and apiVersion.

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 opens with a specific verb and resource: 'PRICE A BET SLIP — the authoritative, current price for selections you are about to back.' It clearly distinguishes this tool as the pre-placement pricing call and names the related sportsbet_place_bet workflow, so an agent can understand what it does even among many betting tools.

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?

The description gives explicit timing context: 'Call this IMMEDIATELY before sportsbet_place_bet' and explains why, because placement takes an asserted price rather than a quote id. It does not explicitly mention when-not-to-use or name alternatives like sportsbet_sgm_price, so it falls just short of a 5.

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

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