Skip to main content
Glama

SportStatsAPI

Get racing stats

get_racing_stats
Read-only

Stats from our stored results. kind jockey or trainer: runs, wins, places and strike rate over the last 14 and 30 days, overall and per region. kind course (last 365 days): favourite win rate, top jockeys and trainers by wins, draw by distance band in thirds of the stalls with sample sizes.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get_racing_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesjockey or trainer code (or number) from find_horses or a race card; for a course the racecourse (meeting) code of a race
kindYesjockey, trainer or course

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real context beyond that: results are from stored (not live) data, the aggregation windows are 14 and 30 days for jockey/trainer versus 365 days for course, and course draw stats are bucketed in thirds of the stalls with sample sizes disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose before branching into per-kind detail, with no filler. The second sentence is a dense run-on list that is harder to parse than it needs to be, which keeps it below a 5.

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 return values and does so for both kind branches, including metric names, time windows and sample sizes. It is complete for a two-parameter read tool, though it omits any note on ordering, limits, or how a missing id is handled.

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 100%, so id and kind are already documented, and the description adds meaning rather than repeating it by explaining that the same kind parameter changes both the entity type and the returned metric set. It does not clarify the id format for the course case beyond what the schema says, keeping it just short of a 5.

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 names the resource (stored racing results) and enumerates the exact metrics returned for each kind: runs, wins, places and strike rate for jockey/trainer, and favourite win rate, top performers and draw-by-distance for course. That is concrete enough for an agent to know what it gets, but it never distinguishes itself from siblings such as get_runner_form or get_race_briefing.

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 through the kind branches and the time windows (14/30 days for people, 365 days for courses), which hints at when each mode applies. There is no explicit when-to-use or when-not-to-use statement and no routing to an alternative tool, so the agent must infer selection.

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