ledgerfc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_track_recordD | Honest settled record + high-confidence subset + CLV. |
| get_predictionsB | Upcoming predictions with probabilities and model-vs-market edge. |
| get_arbsC | PRO: recently detected live arbitrage opportunities. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument. |
| get_value_betsA | PRO: upcoming picks with positive model-vs-market edge. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument. |
| searchA | Search upcoming match predictions. Returns {id,title,url} results; use fetch(id) for the full prediction. |
| fetchB | Fetch the full prediction document for a search result id. |
| submit_predictionC | Submit a prediction to be scored by CLV (shadow/points). |
| get_leaderboardB | Contributors ranked by CLV (reputation points, not cash). |
| get_contributor_scoreD | A contributor's CLV record. |
| place_betC | Place a paper bet against our agent's prediction (points only). |
| get_balanceC | Your paper-points balance (not cash). |
| get_my_betsC | Your paper bets, newest first. |
| get_betC | One paper bet by id. |
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 13 tools
Each tool has a clearly distinct purpose: track record, predictions, arbs, value bets, search/fetch pair, submission, leaderboard, contributor score, betting operations. No two tools overlap in a way that would cause misselection.
All tools use consistent lowercase snake_case with a verb_noun pattern. Most start with 'get_', with a few action verbs like 'search', 'fetch', 'submit_prediction', and 'place_bet' that still follow the same style.
13 tools is well within the ideal range for a domain covering predictions, submission, scoring, and betting. Each tool serves a distinct function and none appear redundant.
The surface covers the main lifecycle: viewing predictions, fetching details, submitting predictions, checking leaderboard and contributor scores, placing bets, and viewing balance and bet history. Minor missing operations like updating or canceling bets are not critical for the core workflow.