therundown-data

Official

by TheRundown

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

List sports

list_sports

Read-onlyIdempotent

Retrieve current canonical sport IDs and names to map sports consistently. Use the returned identifiers as references, not as evidence of current events, prices, or plan access.

Instructions

List current canonical sport IDs and names. Do not use a catalog row as evidence of current events, prices, or plan access.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`plan`	No
`empty`	No
`error`	No
`usage`	No
`status`	No
`message`	No
`event_id`	No
`source_url`	No
`retry_after`	No
`limit_reason`	No
`retrieved_at`	No
`required_plan`	No
`remaining_points`	No
`missing_entitlement`	No
`monthly_remaining_points`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "sports": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "sport_id": {
+                "anyOf": [
+                  {
+                    "exclusiveMinimum": 0,
+                    "maximum": 2147483647,
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "sport_name": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "sports"
+      ],
+      "type": "object"
+    },
+    "empty": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "enum": [
+            "page_out_of_range",
+            "no_results"
+          ],
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "scope": {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "scope"
+      ],
+      "type": "object"
+    },
+    "error": {
+      "type": "string"
+    },
+    "event_id": {
+      "type": "string"
+    },
+    "limit_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing_entitlement": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "monthly_remaining_points": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "plan": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "remaining_points": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "required_plan": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "retrieved_at": {
+      "type": "string"
+    },
+    "retry_after": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "source_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "status": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "usage": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedv0.2.1Sep 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds that the returned IDs/names are static catalog metadata not tied to live events/prices, which is genuinely useful context beyond annotations but limited in depth.

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?

Two short sentences with zero waste; the primary purpose is front-loaded and the caveat follows efficiently.

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 an output schema available, the description needn't explain return values. Combined with annotations and full schema coverage, it is complete enough for an agent to call this zero-arg list tool, though it could more explicitly position itself against sibling listing tools.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering arguments are needed.

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?

States a specific verb ('List') and resource ('current canonical sport IDs and names'), making the scope and output explicit. It is clearly distinguishable from siblings like list_events or list_markets, which cover different resources.

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?

Provides a caution ('Do not use a catalog row as evidence of current events, prices, or plan access') that governs downstream usage, but gives no when-to-use guidance relative to alternatives such as list_events or get_main_lines.

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

Deploy Server