Skip to main content
Glama

SportStatsAPI

Get race briefing

get_race_briefing
Read-only

Ready briefing for one horse race from our results: field size, distance, going, class, the favourite, each runner's form figures and last run, jockey and trainer strike rates over the last 30 days; after the race the winner, starting price and whether the favourite won. Each statement also as a sentence (lang de, es, it, fr). Facts only.

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

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
formatNomd for a short Markdown text instead of JSON
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description usefully explains that content changes after the race (winner, starting price, favourite result appear only post-race) — which is the most plausible reason for idempotentHint=false. Beyond that it adds little: no mention of data freshness/caching, what happens for an unknown or not-yet-run race_id, or error behavior.

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 payload list is front-loaded and dense, with the pre-race versus post-race split and the language note packed into three short clauses and two sentences. No filler wording earns a place unnecessarily given how much content is conveyed.

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 field by field, including the post-race fields and the sentence per language. It is slightly short on value formats (distance units, going/class vocabularies) and on failure behavior for an invalid race_id, which keeps it from a 5.

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 the baseline is 3, but the description adds real meaning: it clarifies that lang controls rendering of every statement as a sentence in de/es/it/fr (the schema's own lang text about team, league and country names is boilerplate that does not fit racing). It adds nothing for format ('md') or for the accepted race_id forms, which the schema already covers.

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 a specific verb and resource ('Ready briefing for one horse race') and enumerates the exact payload (field size, distance, going, class, favourite, runner form, strike rates, post-race winner/SP). It is clearly a richer, race-scoped cousin of get_race and get_runner_form, though it never names those siblings to make the distinction explicit.

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 by the content list and by 'from our results' (this tool's own data source), and the pre-race/after-the-race split hints at when it is useful. However, there is no explicit statement of when to choose this over get_race, get_runner_form or find_horses, and no exclusions or prerequisites.

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