Skip to main content
Glama

Horse racing entries from Equibase's free entry pages

sports_equibase
Read-only

Horse racing entries from Equibase's free entry pages for a track and date (e.g. PRX; without a date, the track's next card): race card with purse, type, distance, surface, starters and post time; with a race number, the field with program number, post position, horse, age/sex, medication, jockey, weight, trainer and morning-line odds. US tracks (CAN for Canada). No past performances or results. Related tools on this server, for a different need: sports_korn_ferry_tour_leaderboard when you need Korn Ferry Tour leaderboard for the current or most recent. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "track": "<track>"
    },
    "name": "sports_equibase"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoRace date YYYY-MM-DD (optional; without it the track's next card from today, US Eastern, up to 7 days ahead)
raceNoRace number 1-20 for the field (optional; without it the race card is returned)
trackYesEquibase track code, e.g. BEL, SA, CD, GP, KEE, WO
countryNoUSA (default) or CAN

Output Schema

NameRequiredDescriptionDefault
dateNo
raceNo
trackNo
sourceNo
countryNo
entriesNo
checkedAtNo
trackCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new context: cost ($0.002 per successful call), the x402 payment rails, and that failed calls are not charged. It also states scope limits (US tracks, CAN for Canada) beyond what annotations say, though it says nothing about rate limits or response size.

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?

Front-loaded with the core capability and the two return shapes in a single dense but scannable sentence. The trailing pricing/payment sentence is long and somewhat boilerplate, but it carries decision-relevant cost information, so it 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?

An output schema exists, so return-field enumeration is a bonus rather than a requirement, and pricing, geography, and mode behavior are all covered. Missing only operational details such as card availability timing edge cases or what happens when a track has no upcoming card.

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% and each parameter already carries a description, so the schema does the heavy lifting. The description reinforces mode-switching via race number and supplies PRX as an extra track-code example, but adds no format or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource (horse racing entries from Equibase) plus scoping by track and date, and spells out the two operating modes: race card by default, full field with named attributes when a race number is supplied. An agent can distinguish this from any sibling at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit exclusions ("No past performances or results") and the default behavior when date or race is omitted. The only alternative it routes to is sports_korn_ferry_tour_leaderboard, which covers a different sport, so there is no real guidance between competing horse-racing sources.

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