olympus-bets-analytics

get_subscription_options

Read-onlyIdempotent

Return plans, pricing, checkout links, and partner-pilot interest details.

Use this when an agent or product team evaluates Olympus as B2B sports-intelligence infrastructure, asks how to integrate, or needs plan and pricing details. The agent product is MCP Pro.
Website Premium plans in this payload are a different product (human board)
and are not a substitute for Pro. Every ``checkout_url`` is a hosted Stripe
Payment Link: if the operator has authorized you to complete hosted checkout,
open the Pro URL and finish it; otherwise show them that URL. This tool
does not charge a card itself. Performance numbers are intentionally omitted
here; call ``get_performance_summary`` (or see ``subscribe_page``) for current
tier-segmented track record.

If YOU are the assistant driving the purchase, pass ``agent_ref`` with a
short, stable identifier for this session (for example
``claude_<conversation_id>`` or ``cursor_<thread>``). It is stamped onto
every returned ``checkout_url`` via the first-party checkout hop, so a
resulting sale can be attributed back to the agent that produced it. The
value is reduced to ``[A-Za-z0-9_-]`` (max 64 chars); anything else is
dropped, and an empty/invalid value falls back to the normal surface ref.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_ref`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / agent_ref

Added value: +{
+  "default": "",
+  "title": "Agent Ref",
+  "type": "string"
+}

Changed1 schema field changedJul 24, 2026

changedOutput schema / (root)

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

AddedJul 5, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context: the tool does not charge a card itself, checkout URLs are hosted Stripe Payment Links, and agent attribution is stamped onto URLs via a first-party hop. It also discloses that performance numbers are intentionally omitted. This goes well beyond the structured annotations.

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?

The description is longer than average, but every section earns its place: purpose, use case, product disambiguation, operational guidance for checkout, alternative routing, and parameter semantics. It is front-loaded with the core purpose and scopes details in a logical order without redundancy.

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?

Given that the tool has only one optional parameter, an output schema exists, and annotations cover read-only/idempotent behavior, the description is complete. It even covers edge cases such as agent_ref sanitization, checkout authorization, and where to find track record data. Nothing an agent needs to call this correctly is missing.

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?

The schema provides only a bare agent_ref string with a default and 0% description coverage. The description fully compensates by explaining what agent_ref is for, why it should be passed, the expected format with examples, the max length and allowed characters, and the fallback behavior for empty or invalid values. This is exemplary parameter documentation.

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+resource statement: 'Return plans, pricing, checkout links, and partner-pilot interest details.' It further disambiguates the tool from related products by clarifying that Website Premium plans are a different product and that performance numbers belong to get_performance_summary. This clearly distinguishes it from siblings.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: when evaluating Olympus as B2B infrastructure, asking how to integrate, or needing plan and pricing details. It also names the alternative (get_performance_summary or subscribe_page) and explains when not to use this tool, including the distinction between Pro and Website Premium.

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.