puntersedge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUNTERSEDGE_API_KEY | Yes | Your PuntersEdge API key. Get one at https://puntersedge.online/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| racing_next_to_goA | The next Australian horse, greyhound and harness races about to jump, with EVERY bookmaker's price for every runner side by side. This is the primary tool: use it for 'what's racing next', 'who is favourite in the next race at ', or any question about current Australian racing prices. Each race reports data_age_seconds and each price its own age, so you can tell the user how fresh the odds are rather than implying they are live to the second. |
| racing_best_oddsA | The single best available price for each runner in upcoming Australian races, and which bookmaker is offering it. Use this when the user wants the best price rather than a full comparison across every book — 'where is the best odds on ', 'best price in the next race'. |
| racing_eventsA | The upcoming Australian race schedule — venues, race numbers and jump times, without runner prices. Use this for 'what meetings are on today' or to find a race_id before asking about it. Cheaper than next_to_go when prices are not needed. |
| racing_resultsA | Settled results for Australian races that have already run — finishing order and dividends. Use this for 'who won the at ' or to check a past result. Not for upcoming races. |
| racing_moversA | Runners whose price has moved sharply across the market — firming (shortening) or drifting (lengthening). Use this for 'what's being backed', 'any big movers today', or market-sentiment questions. A move confirmed by several bookmakers is more meaningful than one book repricing, so min_books guards against reading noise as a signal. |
| list_sportsA | Every sport and competition this API currently covers, with its sport_key. Call this FIRST if you are unsure of the right sport_key — passing an unknown key returns a 404 listing the valid ones, but checking here is cheaper. Note there is no 'horse-racing' sport_key: racing lives under the separate racing_* tools. |
| get_sports_oddsA | Head-to-head and other market odds for one sport, from every bookmaker covering it. Use for 'odds for the game', 'who is favourite in the NRL tonight'. Sports coverage is thinner than racing — at most 5 bookmakers on AFL and NRL, 3 on NBA and ATP, and as few as 1 on some competitions — so say how many books are quoting rather than implying a full market. |
| get_best_oddsA | The single best price per selection for one sport, and which bookmaker offers it. Use when the user wants the best available price rather than every book's line. |
| account_usageA | This API key's credit usage and remaining balance for the month. Use it when a call has been refused with a 402, or when the user asks how much of their quota is left. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct purpose, but racing_next_to_go and racing_best_odds both cover upcoming racing prices, and get_best_odds vs racing_best_odds have similar names across domains. Descriptions clearly distinguish all-bookmakers from best-price, so misselection risk is low.
Tool names mix verb-based patterns (get_, list_) for sports and account with a racing_* prefix for all racing tools. The racing_* group is internally consistent, but the overall set lacks a uniform verb_noun convention, making the naming somewhat inconsistent.
With 9 tools, the server is well-scoped for a betting odds API covering both sports and racing. Each tool covers a distinct function with no obvious bloat or redundancy.
The API covers account usage, sports odds (all and best), racing schedule, live prices, best odds, movers, and results. A minor gap is the lack of a direct way to fetch odds for a specific race by ID, relying instead on next-to-go or best-odds for upcoming races.