fantasy-yolo
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_matchupC | Who you are playing this week, and the projected score for both sides. |
| get_rosterB | Your roster: lineup slots, NFL opponents, projections and injury designations. Injury designations are exactly what ESPN reports. There is no timestamp and no news text behind them, so do not describe how recent one is (B-02). |
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 2 tools
get_matchup and get_roster target completely different resources: one provides weekly opponent and projected scores, the other provides team roster details. There is no overlap or ambiguity between them.
Both tools follow the exact same get_<noun> snake_case pattern, making the naming predictable and easy to understand.
Two tools is borderline: they cover the core read-only queries for a fantasy matchup and roster, but the server is sparse compared to the typical footprint of a fantasy football tool.
The server is entirely read-only and limited to matchup and roster information. There are no tools for lineup changes, player news, league standings, or transactions, which are significant gaps for fantasy football workflows.