Skip to main content
Glama

SportStatsAPI

Get races

get_races
Read-only

Horse races of a day (default today, UTC), optionally of one region or racecourse: off time, course, race name, distance, going, class, number of runners, status (NS, live, result_pending, FT, unlisted).

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": "get_races"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoUTC race day YYYY-MM-DD (default today)
limitNomax races (default 20, max 100)
offsetNoskip this many races (paging)
regionNousa, uk (Great Britain), ie (Ireland), australia, hk, singapore, dubai, sa or france
meeting_idNoracecourse (meeting) code (or number) from a race

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"usa, uk, australia, hk, singapore, dubai, sa or france"New value: +"usa, uk (Great Britain), ie (Ireland), australia, hk, singapore, dubai, sa or france"
  2. Changed2 schema fields changed
    • changedInput schema / properties / meeting_id / description
      Previous value: -"racecourse (meeting) id from a race"New value: +"racecourse (meeting) code (or number) from a race"
    • changedInput schema / properties / meeting_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered before the description is read. The description adds the status vocabulary (NS, live, result_pending, FT, unlisted) which is genuinely useful behavioral context, but says nothing about result volume, how partially-settled days behave, or how offset interacts with live races changing status.

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?

A single dense sentence that front-loads the default scope and then the optional narrowing, with no filler or repeated title text. The field enumeration at the end is compact and earns its place because no output schema exists.

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 no output schema, the description carries the return-shape burden and does so by listing the fields an agent will receive plus the status codes. It is close to complete for a paged list tool, with the only real gap being how paging behaves against a live, changing day.

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%, so date format, limit bounds, offset paging, region values and meeting_id are already documented in the schema. The description reinforces the defaults and the region/racecourse intent but adds no syntax or format meaning beyond that, which is the baseline case for a fully described schema.

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 the resource precisely (horse races), the default scope (a single day, UTC), and the optional narrowing axes (region, racecourse), then enumerates the fields returned. It is clearly distinguishable from a singular race lookup, but it never names a sibling or explicitly contrasts with get_race or find_horses.

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?

Usage is implied rather than stated: the agent learns it can pass a region or a meeting_id to narrow results, and that omitting both yields today's races. There is no explicit guidance on when to prefer get_race for a single race, when to page versus widen filters, or any stated exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources