olympus-bets-analytics

get_track_record

Read-onlyIdempotent

Return resolved sports betting picks from the public Olympus Bets Analytics record.

Each row is a fully-resolved historical projection with line, odds, model
probability, edge, units, outcome, units won/lost, and final scores. The record is timestamped and publicly auditable. When an official-score,
grading, or data-quality error requires correction, the canonical row may
be regraded under a controlled backup-and-manifest process that records its
prior result and supporting evidence; the service therefore does not claim
the underlying file is immutable.

Args:
    league: Filter by league (NBA, NHL, MLB, CBB, NFL, SOCCER, LOL, GOLF, TENNIS).
    result: Filter to WIN, LOSS, or PUSH only.
    tier: Filter to public free rows, masked premium rows, or masked
        Premium Leans rows (``lean`` — flat 0.5u model disagreements with
        the price, graded in their own column, never blended into
        ``premium``; masked identically to premium rows since leans are
        paid content — matchup/result/units only, no line/odds/edge).
    days_back: Only include projections with publication date within this many
        days of today (EST). Default 30.
    limit: Maximum rows to return (capped at 500).
    cursor: Zero-based result offset for stable pagination.

Returns:
    ``{filter, count, summary: {wins, losses, pushes, voids, other,
    cross_tier_duplicates, units_won}, excluded: {...}, picks: [...]}``
    ``total_matching`` always equals ``summary.wins + losses + pushes +
    voids + other + cross_tier_duplicates`` -- every row counted in
    ``total_matching`` lands in exactly one disclosed bucket. A wager
    published on two tiers counts once in a mixed-tier summary; its
    second tier's row is in ``cross_tier_duplicates``. ``excluded`` is a separate, all-time
    (not filtered by this call's args) count of what never reaches this
    population at all. Picks are newest-first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_track_record"
  }
}

Input Schema

Name	Required	Description	Default
`tier`	No
`limit`	No
`cursor`	No
`league`	No
`result`	No
`days_back`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / tier / anyOf

Previous value: -[
-  {
-    "enum": [
-      "free",
-      "premium"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "free",
+      "premium",
+      "lean"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed3 schema fields changedJul 24, 2026

addedInput schema / properties / cursor

Added value: +{
+  "default": 0,
+  "title": "Cursor",
+  "type": "integer"
+}

addedInput schema / properties / tier

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "free",
+        "premium"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Tier"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_track_recordDictOutput",
+  "type": "object"
+}

First observedJun 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only and idempotent behavior, but the description adds material context the annotations cannot: the regrade path for official-score or grading errors, the explicit disclaimer that the underlying file is not immutable, the all-time vs. filtered distinction for 'excluded', and cross-tier deduplication. These are exactly the non-obvious traits an agent needs to describe results honestly, though the Returns block partly duplicates the output schema.

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?

Purpose is front-loaded, and the Args/Returns structure is easy to scan. A few sentences run long — the tier/'lean' explanation and the total_matching bucket arithmetic are dense — but nearly every clause carries information an agent would otherwise have to guess.

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 six-parameter, zero-required read tool whose output schema exists, this is close to complete: it covers filtering, masking, pagination, deduplication accounting, and the correction process. The small remaining gap is that it never explains how this record relates to the other history tools, which matters at this sibling density.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: it enumerates valid league values (absent from the schema, which has a bare string), explains the three tier values including what a masked 'lean' row exposes, states the limit cap of 500, and defines cursor as a zero-based offset for stable pagination. Defaults and the EST basis for days_back are also supplied.

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 opening sentence gives a specific verb and resource ('Return resolved sports betting picks from the public Olympus Bets Analytics record') and adds scope ('fully-resolved historical projection'). It does not, however, distinguish itself from near-identical siblings such as get_pick_history, get_projection_history, or get_premium_history, leaving the agent to infer the split from the filter list.

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?

Usage is only implied through the filter semantics (league/result/tier/days_back) and the default 30-day window. There is no explicit 'use this when...' guidance and no statement about when to prefer get_pick_history or get_premium_history instead, which is a real gap given three overlapping siblings.

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

All olympus-bets-analytics 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.