Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

One race, every bookmaker

race_odds
Read-onlyIdempotent

One upcoming race in full: every runner with every bookmaker's win, place and (where offered) top 2/3/4 price, each book's quote age, scratchings and race conditions. Give the venue plus race_number or race_id; with only a venue you get that venue's next race. The call is billed even when the race is not on the live board (already run or not yet priced); the reply then lists the races that are. Costs 2 credits. Every plan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue": "<venue>"
    },
    "name": "race_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueYesVenue name as the feeds spell it, case-insensitive, e.g. Randwick or Sandown Hillside.
countryNoISO country code(s), comma-separated: AU, NZ, GB (Britain, not UK), IE, ZA, e.g. 'AU' or 'GB,IE'.
race_idNorace_id from odds_board, race_card, race_results or the archive. The most reliable way to name a race.
bookmakersNoOnly these bookmaker keys, e.g. ["tab", "sportsbet", "ladbrokes_au"]. Default: every book. An unknown key is refused free of charge with the list of valid keys.
race_numberNo

Output Schema

NameRequiredDescriptionDefault
raceYes
other_races_at_venueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses cost (2 credits), that billing occurs even when the race is not on the live board, and that the reply will then list races that are. It also confirms availability on every plan, adding meaningful operational context.

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 tightly front-loaded: first what the response contains, then how to address the race, then billing/fallback behavior. Every sentence carries useful information with no wasted text.

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

Completeness4/5

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

With an output schema and rich annotations already present, the description covers the important invocation, cost, and not-on-board behavior. The only notable omission is explicit routing guidance against sibling odds tools.

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 high at 80%, so the baseline is 3. The description adds useful combination semantics: venue plus race_number or race_id, and venue-only returning the next race, which helps an agent choose parameters correctly.

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 states a specific resource and scope: one upcoming race with every runner, every bookmaker's win/place/top 2-3-4 prices, quote ages, scratchings and race conditions. It clearly distinguishes this full single-race odds view from broader board or best-price tools, even without naming siblings explicitly.

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

Usage Guidelines3/5

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

It explains how to name the race: venue plus race_number or race_id, with venue alone returning that venue's next race. It does not explicitly say when to use this versus siblings such as odds_board, race_markets or best_odds, so alternative-selection guidance is only implied.

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

All puntersedge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources