Skip to main content
Glama
Sign In

puntersedge

by io.github.Propertyscout001
OverviewDiscussionsAdmin

All markets for one race

race_markets
Read-onlyIdempotent

Every bookmaker's prices for one race across win, place and top 2/3/4, plus exotic dividends once settled. Live prices before the jump, each book's closing price after it. Give race_id, or venue + meeting_date + race_number. Costs 2 credits. Plan: Plus and above.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "race_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNoVenue name as the feeds spell it, case-insensitive, e.g. Randwick or Sandown Hillside.
countryNoTwo-letter country of the meeting. Only needed when two meetings share a venue name on one day (Ascot in Perth and in Berkshire).
marketsNoMarkets to include. Default: all.
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
meeting_dateNoMeeting day, YYYY-MM-DD, Australian Eastern time.

Output Schema

NameRequiredDescriptionDefault
dataYesThe API response, with links and empty fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, but the description adds meaningful operational context: a 2-credit cost, a Plus-and-above plan requirement, live prices before the jump, closing prices after the jump, and exotic dividends only once settled.

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 four tight sentences with zero filler. Scope is front-loaded, then temporal behavior, then input alternatives, then cost and plan requirements.

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?

Given seven optional parameters, high schema coverage, an output schema and full read-only annotations, the description covers the key missing context: what is returned, cost, plan eligibility and race-identification fallbacks. It could mention partial-failure or empty-result behavior, but the essential picture is complete.

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 86%, so the schema already documents individual parameters well. The description adds useful alternative identification logic: use race_id, or fall back to venue + meeting_date + race_number, which is not obvious from the individual field descriptions alone.

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?

States precisely what the tool returns: every bookmaker's prices for one race across win, place, top 2/3/4 and exotic dividends. It clearly distinguishes the resource scope from broad market summaries, though it does not explicitly name sibling tools like odds_board or race_odds.

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?

The description gives the two ways to identify a race (race_id or venue + meeting_date + race_number) and notes live vs closing-price phases, which implies usage. However, it does not state when to prefer this tool over alternatives such as race_odds, odds_board or market_summary.

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