puntersedge

Race results

race_results

Read-onlyIdempotent

Settled results: placings with settled prices, starting prices where published, and dividends. Use date for a past day or hours_back for the latest. Costs 2 credits. Every plan.

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_results"
  }
}

Input Schema

Name	Required	Description
`date`	No	Meeting day, YYYY-MM-DD, Australian Eastern time.
`limit`	No
`venue`	No	Venue name as the feeds spell it, case-insensitive, e.g. Randwick or Sandown Hillside.
`offset`	No
`status`	No
`country`	No	ISO country code(s), comma-separated: AU, NZ, GB (Britain, not UK), IE, ZA, e.g. 'AU' or 'GB,IE'.
`categories`	No	Racing codes to include. horse = thoroughbreds. Default: all three.
`hours_back`	No

Output Schema

Name	Required	Description	Default
`data`	Yes	The API response, with links and empty fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds valuable context not in annotations: the tool costs 2 credits, is available on every plan, and returns settled prices and dividends. It does not cover auth or rate-limit behavior, but the cost note is meaningful.

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 three short sentences with the core result content front-loaded, followed by the date/hours_back choice and the cost. Every sentence carries actionable information and there is no filler.

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

Completeness3/5

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

The presence of an output schema means return values need less explanation, and annotations cover the safety profile. However, for an 8-parameter tool with 50% schema coverage, the description does not explain key filtering parameters such as status, venue, country, or categories, leaving gaps in how to scope a results query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 8 parameters with 50% schema description coverage. The description adds meaning only for 'date' versus 'hours_back'; it does not explain 'status' (final/interim/abandoned), 'limit', 'offset', or how 'venue', 'country', and 'categories' combine when filtering results.

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 states a specific resource ('settled results') and enumerates what it returns: placings with settled prices, starting prices, and dividends. It is clearly distinct from live-odds siblings like race_odds and odds_board, though it does not explicitly name a sibling alternative.

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 gives useful temporal guidance: use 'date' for a past day or 'hours_back' for the latest. However, it does not say when to use this instead of race_card, race_form, or other result-adjacent tools, nor does it explain filtering or pagination context.

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

All puntersedge tools Inspect

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.