TheRundown Data MCP

Get closing lines for a sport and date

v1GetClosingBySportAndDate

Read-onlyIdempotent

Get closing lines for a sport and date Read-only Product data or price calculation. Use returned canonical IDs. Access, delay and metered usage follow your connected account; never infer coverage from an empty result. One bounded request, no background polling or automatic retry. Affiliate 27 is excluded. No wagers, account changes or guarantee of returns.

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": {
      "path": "<path>"
    },
    "name": "v1GetClosingBySportAndDate"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`query`	No

Output 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.

AddedOct 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real context beyond that: metered/account-bound access, no background polling or automatic retry, one bounded request, and that empty results do not imply zero coverage. The 'no wagers, account changes' line largely restates readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the sentence is missing punctuation between 'date' and 'Read-only', and the remainder is a dense run-on of clauses of mixed relevance. It is not padded so much as poorly structured.

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?

For a read-only query tool with full annotations and an output schema (so return values need no explanation), the description covers the important operational caveats: metering, no retry, exclusion, and empty-result semantics. The remaining gap is sibling differentiation (v1 vs v2 closing) and parameter-level guidance.

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 description itself contributes nothing about parameters. The reported 0% schema coverage is misleading here: the schema actually documents sportID (with enumerated common values), offset (UTC minutes), affiliate_ids (sportsbook IDs plus the sentinel behavior), and event_status inline. With that in-schema richness, baseline 3 is appropriate, but the description earns no credit.

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 first sentence states a specific verb and resource ('Get closing lines for a sport and date'), so the agent knows what the tool returns. However, it is verbatim identical to the title and does not distinguish it from near-identical siblings such as v2GetClosingBySportAndDate or v1GetOpenersBySportAndDate, so the agent cannot tell which closing-lines variant to pick.

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?

It implies usage ('Use returned canonical IDs', 'never infer coverage from an empty result') and states an exclusion (Affiliate 27), which is genuinely useful. But it never says when to choose this v1 closing tool over the v2 sibling, an opener tool, or a moneyline tool, so the selection guidance is only implied.

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

All TheRundown Data MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.