Skip to main content
Glama

olympus-bets-analytics

by com.olympus-bets
OverviewDiscussionsAdmin

get_premium_slate

Read-onlyIdempotent

Return today's protected premium slate for an entitled agent.

Requires ``Authorization: Bearer obmcp_...``. MCP Connect and MCP Pro are
both accepted. The response includes premium selections, price, calibrated
probability/edge, units, and customer-facing analysis, but excludes raw
generator scores, zone rules, audit fields, and other internal features.
Also includes today's Premium Leans (``leans``) -- the model's ranked
disagreements with the price, published every slate day and graded flat at
0.5u in their own track-record column; they are not Kelly-sized picks.

``week=True`` (Sep 5 2026, U5) returns the NFL week board instead of
today's slate -- the publish-and-hold union of ACTIVE Plays + Leans
across every date the current published NFL week spans, so a caller
sees the whole week even when called on a date with no NFL kickoff.
NFL-only: ``league`` is forced to NFL when omitted and must be NFL
(case-insensitive) when given alongside ``week=True``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weekNo
limitNo
leagueNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / week
      Added value: +{
+  "default": false,
+  "title": "Week",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint, so the description carries the behavioral burden and handles it very well. It discloses exactly which fields are included and excluded from the response, describes Premium Leans as 0.5u flat-graded non-Kelly picks, and explains the publish-and-hold week semantics. This is substantial transparency beyond the annotations.

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 the core action and then organized into focused paragraphs for auth, response contents, Leans, and week mode. It is longer than average but each section adds necessary operational detail; only the limit parameter's absence prevents it from being fully tight.

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

Completeness5/5

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

For a tool with three optional parameters, auth requirements, and meaningful response-shaping behavior, this description is remarkably complete. It covers entitlement, authentication, response inclusions/exclusions, the Leans distinction, week-mode semantics, and league validation. The limit parameter is a minor omission against an otherwise comprehensive definition.

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 0%, so the description must compensate. It richly explains week and league, including the NFL-only constraint and case-insensitivity, but the limit parameter is never mentioned. With three parameters and one of them left completely unaddressed, the compensation is good but incomplete.

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?

The description opens with a specific verb and resource: 'Return today's protected premium slate for an entitled agent.' It goes further by distinguishing the week mode and the Premium Leans component, which clarifies what this tool uniquely provides relative to other get_* siblings.

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

Usage Guidelines4/5

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

The description gives clear usage context: it requires a Bearer obmcp_... token, names which product tiers are accepted, and explains when to use week=True versus the default today behavior. It does not explicitly name alternative tools or state when not to use this one, so it stops short of a 5.

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

Resources