BeatLeader Helper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEATLEADER_PLAYER_ID | No | Default player ID for stdio entry point; an explicit player argument takes priority | |
| BEATLEADER_PUBLIC_URL | No | HTTPS origin for an additional custom domain, e.g. https://mcp.example.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_playerA | Get a public player profile by ID, alias, or profile URL. Select stats, clans, socials, and badges with include; defaults to basic profile. Returns sources, context, data, and section availability. Accuracy uses percentages and times use ISO 8601 |
| search_playersA | Search public players by nickname, country, total PP range and PP component sorting. Returns candidates with stable IDs; select an ID before querying a player |
| search_mapsA | Search leaderboard difficulties by song, ranked status, stars, Acc/Pass/Tech ratings, mode and BeatSaver mapper IDs. Results can be passed to get_leaderboard |
| list_player_scoresB | List current scores with pagination, percentage accuracy bounds, modifiers, dates, stars, difficulty, mode and song filters. Accuracy is 0–100; dates use ISO timestamps with timezones |
| get_player_historyA | Get 1–90 daily public player snapshots and calculate changes over actual returned dates, with percentage accuracy and ISO timestamps |
| get_leaderboardB | Get map details and leaderboard scores to inspect difficulty, base ratings, and score conditions |
| analyze_playerA | Read up to five pages of fifty current scores, compute grouped percentage statistics, and suggest previously played maps for practice; includes coverage and sample limits. Supports general, noMods and noPause |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target clearly distinct resources and actions, such as player lookup, player search, map search, and score history. The only mild overlap is between list_player_scores and analyze_player, since both deal with current scores, but their purposes are separated by listing versus statistical analysis.
All tool names follow a consistent lowercase snake_case verb_noun pattern, such as get_player, search_players, list_player_scores, and get_leaderboard. There are no mixed naming conventions or vague generic verbs.
Seven tools is a well-scoped size for a BeatLeader helper, covering player profiles, search, score listing, history, leaderboards, and analysis. Each tool has a clear role and none feel redundant or unnecessary.
The tool surface covers the main read-only workflows an agent would need: finding players, retrieving profiles, searching maps, viewing leaderboards, listing scores, examining history, and analyzing performance. The search tools feed cleanly into the detail tools, so there are no obvious dead ends or major missing operations.