com.olympus-bets/olympus-bets-analytics: tool descriptions scored

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://app.olympus-bets.com/mcp
Homepage: app.olympus-bets.com
Repository: github.com/drduda9/olympus-bets-mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how com.olympus-bets/olympus-bets-analytics's tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/com.olympus-bets/olympus-bets-analytics

Average score: 61.0 / 100Cloudy
Tools: 24
Near-identical descriptions: 1

Across the server

Minor
The server's instructions are 3202 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
get_team_profile	get_player_profile	0.75	0.50

Tools

get_player_profile

40 / 100Cloudy

Purpose: 13 / 20
When to use: 0 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: league, player.param_no_description
Minor
Its description is nearly the same as get_team_profile's (similarity 0.75); only the names and schemas tell them apart. Say in this description when to use get_team_profile instead.confusable_pair
Minor
String arguments with no constraint or example: player.loose_string_param

get_team_profile

40 / 100Cloudy

Purpose: 13 / 20
When to use: 0 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: league, team.param_no_description
Minor
Its description is nearly the same as get_player_profile's (similarity 0.75); only the names and schemas tell them apart. Say in this description when to use get_player_profile instead.confusable_pair
Minor
String arguments with no constraint or example: team.loose_string_param

search_entities

40 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 5 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: query, league, entity_type, limit.param_no_description
Minor
String arguments with no constraint or example: query.loose_string_param

get_market_fair_value

50 / 100Cloudy

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 3 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: league, date, team.param_no_description
Minor
String arguments with no constraint or example: league.loose_string_param

get_premium_history

50 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: league, result, days_back, limit, cursor.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_data_status

52 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

Major
Arguments without a description: league, date.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_engine_versions

52 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: league.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_player_prop_history

53 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 3 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: league, date_from, date_to, player, market, recommended_only, limit, cursor, include_alt_lines.param_no_description
Minor
String arguments with no constraint or example: league.loose_string_param
Minor
The meaning of the boolean argument recommended_only is unclear.vague_boolean
Minor
The meaning of the boolean argument include_alt_lines is unclear.vague_boolean

get_premium_game_recommendation

53 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 3 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Arguments without a description: query, league.param_no_description
Minor
String arguments with no constraint or example: query.loose_string_param

get_projection_history

53 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 8 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: league, date_from, date_to, market, team, player, decision, result, quality, min_edge_pp, limit, cursor.param_no_description

get_todays_projections

57 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: league, verbose.param_no_description
Minor
No `required` list, so every argument is optional.no_required
Minor
The meaning of the boolean argument verbose is unclear.vague_boolean

get_game_recommendation

62 / 100Cloudy

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: league, team, date.param_no_description
Minor
String arguments with no constraint or example: team.loose_string_param

get_subscription_options

65 / 100Cloudy

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: agent_ref.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_model_vs_market

67 / 100Cloudy

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: league.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_performance_summary

67 / 100Cloudy

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: tier, league, detail, window.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_league_schedule

70 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 8 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Arguments without a description: league, date.param_no_description

get_oracle_board

70 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: sport, limit.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_oracle_insights

70 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: sport, limit.param_no_description
Major
It may be destructive, but destructiveHint is not set.destructive_unmarked
Minor
No `required` list, so every argument is optional.no_required

get_pick_history

70 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: league, tier, result, limit, verbose, cursor.param_no_description
Minor
No `required` list, so every argument is optional.no_required
Minor
The meaning of the boolean argument verbose is unclear.vague_boolean

get_player_props

70 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: league, date, game, player, market, limit, lines.param_no_description
Minor
The description is long (430 words). It helps selection but costs steps and tokens.too_long
Minor
String arguments with no constraint or example: league.loose_string_param

get_track_record

70 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: league, result, tier, days_back, limit, cursor.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_premium_slate

75 / 100Clear

Purpose: 20 / 20
When to use: 20 / 20
Arguments: 5 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Arguments without a description: league, limit, week.param_no_description
Minor
No `required` list, so every argument is optional.no_required
Minor
The meaning of the boolean argument week is unclear.vague_boolean

get_brand_card

82 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 25 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

get_methodology

87 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 25 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers