Skip to main content
Glama

racingpulse

Analyze global horse racing data including live odds, going conditions, form analysis, speed ratings, and arbitrage detection for 35 racecourses.

Instructions

RacingPulse: Global horse racing intelligence — live odds, going conditions, form analysis, arbitrage detection, speed ratings, and betting systems for 35 racecourses. All endpoints require x402 payment (USDC on B

Coverage: Global

Endpoints: • scanner ($0.07): Arbitrage scanner — scan all active racing sports for guaranteed-profit opportunities • arbitrage ($0.07): Live arbitrage — filtered guaranteed-profit opportunities for a specific racing jurisdiction • card ($0.07): Race card — complete meeting briefing with runners, odds, going, and news • going ($0.07): Going conditions — live ground conditions derived from 7-day precipitation data • form ($0.07): Form guide — deep horse form analysis with trainer stats and going preferences • ratings ($0.07): Speed ratings — official rating, RPR, Timeform, and going-adjusted performance ratings • systems ($0.07): Betting systems — statistically-backed angles, trainer/jockey combos, draw bias • trends ($0.07): Race trends — historical patterns, draw bias, trainer records, value and fade angles • track ($0.07): Track profile — complete racecourse intelligence with live going conditions • greyhound-form ($0.07): Greyhound form — recent runs, sectional times, trap record, kennel form, and verdict • greyhound-trap ($0.07): Greyhound trap bias — win rates per trap, rail vs wide advantage, pace profile, and betting angles • greyhound-card ($0.07): Greyhound race card — full field breakdown with trap suitability, value selection, and system plays • calculator ($0.07): Betting calculator — arbitrage stakes (Kelly), expected value, and profit calculations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: scanner | arbitrage | card | going | form | ratings | systems | trends | track | greyhound-form | greyhound-trap | greyhound-card | calculator
langNoResponse language code (en | es | fr | de | zh | hi | ar | pt | ja | ko | etc.)
regionsNoregions
sportNosport
min_profitNoMinimum profit % filter
trackNoTrack name e.g. ascot, cheltenham, flemington
dateNodate
horseNoHorse name
trainerNoTrainer name (optional)
filterNoe.g. 'Ascot sprints', 'novice hurdlers', 'flat handicaps'
raceNoRace or meeting name e.g. 'Cheltenham Gold Cup', 'Royal Ascot'
dogNoGreyhound name
distanceNoRace distance e.g. 400m, 460m, 520m
gradeNoRace grade e.g. A1, A2, S2, OR
modeNomode
bankrollNoTotal bankroll (arb mode)
oddsNoComma-separated runner odds e.g. 3.5,2.1 (arb mode)
single_oddsNoDecimal odds for single selection (ev mode)
true_probNoYour estimated true win probability 0-1 (ev mode)
stakeNoStake amount (ev mode)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions a payment requirement and coverage, but lacks disclosure on rate limits, authentication details, data freshness, or consequences of errors. Behavioral traits beyond the basic endpoints are absent.

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 description is verbose and includes pricing and coverage details upfront before listing endpoints. While it is structured as a list, the initial sentences could be more concise. The length is not excessive, but some information could be shortened or moved to annotations.

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

Completeness2/5

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

Given the complexity (20 parameters, multiple endpoints, no output schema), the description lacks usage examples, parameter dependencies, and response information. It provides endpoint purposes but not enough to fully understand how to construct requests or interpret results.

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%, but parameter descriptions are minimal (e.g., 'regions', 'date', 'mode'). The tool description adds context by listing endpoints and some parameter examples, but does not sufficiently explain parameter relationships or advanced usage. Baseline 3 is appropriate.

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 description clearly states the tool is for global horse racing intelligence, listing many specific endpoints that cover odds, form, betting systems, etc. It differentiates from siblings by focusing on racing, but the purpose is somewhat cluttered with pricing and an extensive endpoint list.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description mentions payment requirements but does not provide context for selecting among the many actions or comparing with sibling tools. Usage is implied but not clarified.

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/GTCC777/pulsenetwork-mcp'

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