Skip to main content
Glama

olympus-bets-analytics

by com.olympus-bets

get_engine_versions

Read-onlyIdempotent

Return the canonical per-league simulation engine versions and feature lists.

Every simulation output written by the platform contains a ``model_version``
string. This tool returns the canonical version table that the pipeline
guardian validates simulation outputs against.

Args:
    league: Optional league filter (e.g. "NBA"). Omit to return all leagues.

Returns:
    ``{count, engines: [{league, engine, version, key_features, ...}]}``

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leagueNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_engine_versionsDictOutput",
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds behavioral context by explaining the tool's role in validating simulation outputs against the version table, which goes 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 concise, front-loads the purpose, and includes a brief background. However, the use of backticks and formatting for the return type adds minor clutter; could be slightly more streamlined.

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 simple tool with one optional parameter and an output schema indicated, the description covers all essential aspects: purpose, input filter, and output structure. It is complete and leaves no ambiguity.

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 schema has 0% description coverage, leaving the description to explain the single parameter. It does so effectively by describing the league filter with an example and noting the effect of omission, adding meaning beyond the schema's property title.

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 title and description clearly state that the tool returns the canonical per-league simulation engine versions and feature lists. It provides specific context about the model_version string and pipeline guardian validation, making the purpose distinct from sibling tools which focus on other data.

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?

The description explains when the tool is useful (to retrieve the canonical version table for validation) but lacks explicit guidance on when not to use it or alternatives. It mentions an optional league filter but no further usage context.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools occupy overlapping historical/performance territory: get_track_record, get_pick_history, get_premium_history, get_projection_history, and get_performance_summary all query resolved picks or performance, and get_pick_history even instructs callers to prefer get_track_record. While the long descriptions help, the name-level boundaries are unclear and an agent selecting by tool name could easily choose the wrong history endpoint.

Naming Consistency5/5

Tool names follow a consistent get_<noun> snake_case convention, with search_entities as the only deviation but still a verb_noun form. The naming pattern makes the API predictable and scannable.

Tool Count3/5

Twenty tools is on the heavy side for a single MCP server and falls in the borderline 16-25 range. The count is not absurd, but several history/record tools could likely be consolidated into fewer endpoints.

Completeness4/5

The server covers the main analytics workflow well: data status, methodology, schedules, projections, premium content, performance, historical records, profiles, and subscription details. Minor gaps exist (e.g., no single all-league schedule endpoint, no generic search across all data types), but core querying needs are satisfied.

Resources