Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

tab_racing_race

Read-onlyIdempotent

Retrieve a complete racecard for one race: runners with odds and form, pools, bet types, plus results and dividends once the race has run.

Instructions

Full racecard for one race: runners with fixed + parimutuel odds, form ratings, pools, bet types; results + dividends once run.

Returns: {raceNumber, raceName, raceDistance, raceStartTime, runners:[{runnerNumber, runnerName, fixedOdds, parimutuel, riderDriverName, barrierNumber, last5Starts}], results, pools, betTypes, multiLegApproximates}

Auth: works without a key; TAB_CLIENT_ID or TAB_CLIENT_SECRET or TAB_REFRESH_TOKEN unlocks more if set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesMeeting date, YYYY-MM-DD. Required — part of the URL path.
raceTypeYesRace code: R/G/H. Required — part of the URL path.
raceNumberYesRace number at the meeting. Required — part of the URL path.
jurisdictionNoState jurisdiction.NSW
venueMnemonicYesVenue code, e.g. HAW. Required — part of the URL path.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.24.0
    • addedInput schema / properties / date / description
      Added value: +"Meeting date, YYYY-MM-DD. Required — part of the URL path."
    • addedInput schema / properties / jurisdiction / description
      Added value: +"State jurisdiction."
    • addedInput schema / properties / raceNumber / description
      Added value: +"Race number at the meeting. Required — part of the URL path."
    • addedInput schema / properties / raceType / description
      Added value: +"Race code: R/G/H. Required — part of the URL path."
    • addedInput schema / properties / raceType / enum
      Added value: +[
+  "R",
+  "G",
+  "H"
+]
    • addedInput schema / properties / venueMnemonic / description
      Added value: +"Venue code, e.g. HAW. Required — part of the URL path."
  2. Addedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds meaningful context beyond annotations by explaining auth behavior (works without a key, more unlocks with credentials) and that results/dividends appear once the race has run.

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?

The description is front-loaded with a concise summary, followed by a compact return-shape block and an auth note. Each section earns its place, especially since there is no output schema, though the return-shape block is somewhat detailed.

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?

Given the lack of an output schema, the description compensates well by listing the return fields and runner sub-fields. Required parameters are fully documented in the schema, auth is clarified, and the tool's open/read-only nature is covered by annotations. It is complete enough for an agent to invoke correctly, though it omits explicit differentiation from similar racing tools.

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?

The input schema has 100% parameter description coverage, including required flags and URL-path notes, so the baseline is 3. The description does not add parameter-level details beyond the schema; its extra detail focuses on the return payload rather than input semantics.

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 clearly states the tool's function: "Full racecard for one race" with runners, odds, form ratings, pools, bet types, and results/dividends once run. This is a specific verb+resource and distinguishes it as a single-race racecard tool, though it does not explicitly name competing sibling tools.

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?

The phrase "Full racecard for one race" implies the tool's scope and when it would be appropriate, and the return-shape description clarifies what data to expect. However, it does not explicitly state when NOT to use it or mention alternatives such as meeting-level or form-only racing tools from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanielTomaro13/sportsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server