Skip to main content
Glama

SportStatsAPI

Get race

get_race
Read-only

One horse race card: runners with number, horse, jockey, trainer, weight, rating, recent form where the feed has it, best current price and morning line; once settled the result (positions, starting prices, finish codes such as PU or F) and results_final.

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": {
      "race_id": "<race_id>"
    },
    "name": "get_race"
  }
}

Input Schema

NameRequiredDescriptionDefault
race_idYesrace code (or number) from get_races

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / race_id / description
      Previous value: -"race id from get_races"New value: +"race code (or number) from get_races"
    • changedInput schema / properties / race_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, it discloses two useful traits: fields are present only 'where the feed has it' (partial data), and results appear 'once settled' along with results_final, which explains why the payload changes over time and is consistent with idempotentHint=false. It stops short of describing error behavior for an unknown or unraced race_id.

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?

One dense but well-structured sentence that front-loads the core payload (runners) and then adds the settled-result case after a semicolon. The field enumeration is long but every item helps an agent decide whether this tool answers the question.

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 burden of describing the return payload and does so thoroughly for both pre-race and settled states. Minor gaps remain around what results_final actually signals and what happens for an invalid race_id, but nothing essential to calling it is missing.

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?

There is a single parameter with 100% schema description coverage, and the schema already states the accepted type (integer or string) and its origin in get_races. The description adds no further semantics about race_id, so the baseline of 3 applies.

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 concretely enumerates what one horse race card contains (runners with number, horse, jockey, trainer, weight, rating, form, price, morning line, plus settled results). That is far more specific than the name alone. It does not, however, contrast itself with get_races or get_race_briefing, so the sibling distinction is left implicit.

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 only implied: it is the single-race detail fetch, and the schema note 'race code (or number) from get_races' hints at the workflow from list to detail. There is no explicit statement of when to use this versus get_races or get_race_briefing, and no exclusions or prerequisites are given.

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