Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tab_race

Retrieves race details by meeting date, meeting name, and race number, since the source lacks a single race ID. Use it to look up a specific race.

Instructions

Get TAB race details. A race is addressed by its meeting date, meeting name, and race number (TAB has no single race id).

Input Schema

NameRequiredDescriptionDefault
api_keyNo
race_typeNoR (thoroughbred), G (greyhound), or H (harness). Default R.
race_numberYesRace number within the meeting
jurisdictionNoState jurisdiction, e.g. VIC (default), NSW.
meeting_dateYesMeeting date, YYYY-MM-DD
meeting_nameYesMeeting name, e.g. Flemington

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.11
    • addedInput schema / properties / jurisdiction
      Added value: +{
+  "description": "State jurisdiction, e.g. VIC (default), NSW.",
+  "type": "string"
+}
    • addedInput schema / properties / meeting_date
      Added value: +{
+  "description": "Meeting date, YYYY-MM-DD",
+  "type": "string"
+}
    • addedInput schema / properties / meeting_name
      Added value: +{
+  "description": "Meeting name, e.g. Flemington",
+  "type": "string"
+}
    • removedInput schema / properties / race_id
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / race_number
      Added value: +{
+  "description": "Race number within the meeting",
+  "type": "string"
+}
    • addedInput schema / properties / race_type
      Added value: +{
+  "description": "R (thoroughbred), G (greyhound), or H (harness). Default R.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "race_id"
-]New value: +[
+  "meeting_date",
+  "meeting_name",
+  "race_number"
+]
  2. Addedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that TAB has no single race id, explaining the composite key, but says nothing about return format, the api_key parameter, rate limits, or what happens with an invalid meeting/race combination.

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 tight sentences, front-loaded with the action and followed by the key clarification. No filler, though the second sentence could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with 6 parameters and no output schema, the description adequately conveys the addressing scheme. However, with zero annotations and an optional api_key, it leaves auth and any fallback behavior unaddressed.

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 description coverage is 83%, so the schema already documents most parameters (including race_type, jurisdiction, and date formats). The description restates the three key identifiers but adds the 'no single race id' framing rather than new syntax or defaults, matching the baseline of 3.

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 (Get) and resource (TAB race details), and the second sentence clarifies exactly what a 'race' is keyed by. It does not name or contrast with the sibling tab_meetings, so an agent must infer the distinction, keeping it short of a 5.

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

Usage Guidelines2/5

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

The description explains the addressing scheme but never states when to use tab_race versus tab_meetings or tab_sports_markets. There is no when-to-use or when-not-to-use guidance, only prerequisite identifiers.

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

Deploy Server

Other Tools