Skip to main content
Glama

SportStatsAPI

Get runner form

get_runner_form
Read-only

Last runs of a horse, jockey or trainer in our stored results, latest first: date, course, distance, going, position and field size, starting price; plus wins, top-three finishes and strike rate over those runs.

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

Input Schema

NameRequiredDescriptionDefault
idYeshorse, jockey or trainer code (or number) from find_horses or a race card
kindNohorse (default), jockey or trainer
limitNoruns (default 10, max 50)

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a read-only, non-open-world call, so the description focuses on adding what they cannot: the data is historical ('in our stored results'), results are ordered 'latest first', and the response includes aggregate wins, top-three finishes and strike rate. It stops short of describing behavior on an unknown id or empty history, but the value added is genuine.

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?

A single dense sentence, but it front-loads the core purpose and then enumerates output fields efficiently with no filler. The semicolon-separated aggregate list is slightly heavy but every clause earns its place.

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 correctly carries the burden of describing return values, and it does so thoroughly. Parameters are fully covered by the schema, so the only remaining gap is edge-case behavior for invalid ids or runners with no stored results.

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 coverage is 100%, so every parameter — id, kind, limit with its default and max — is already documented in the schema. The description adds no syntax, format, or fallback meaning beyond what the schema provides, so the baseline 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?

States a specific verb and resource — retrieving the last runs for a horse, jockey or trainer — and enumerates the returned fields, which makes the tool's job unmistakable. It does not name or contrast with a sibling such as get_racing_stats, so differentiation is left to inference.

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 context is only implied: the id is sourced 'from find_horses or a race card', which hints at the workflow but never says when to pick this over get_racing_stats or get_race. There are no exclusions or prerequisites stated.

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