Prompts

Unitley offers 3 MCP prompts. A prompt is a ready-made request you pick in your client. Unitley fills in your arguments and hands the agent one message with numbered steps, in the order the server instructions ask for: your bankroll first, Unitley's data for every fact and the calculators for the math. weekly-moneyline-value sizes each pick with calc_kelly_stake. player-prop-parlay sizes no stake, since its legs are on one game, and leaves the stake to you.

No prompt saves anything on its own. Each one tells the agent to save a pick or log a bet only when you ask.

Every promptCopy Anchor Link

Running a promptCopy Anchor Link

How a prompt appears depends on your client. Some show prompts in a menu, and some do not show them at all. The tools work either way: you can ask for the same thing in your own words.

In Claude CodeCopy Anchor Link

Claude Code turns each MCP prompt into a command. Type / to see them: Unitley's prompts are listed as /unitley:bankroll-check (MCP) and so on. You can also run one as /mcp__unitley__<prompt>. Pass the arguments after the command, separated by spaces, in the order the table above lists them:

/mcp__unitley__bankroll-check month
/mcp__unitley__weekly-moneyline-value 2026-10-09 2026-10-15

player-prop-parlay needs a game's id first, which you get from get_week_slate. Then add the number of legs:

/mcp__unitley__player-prop-parlay 3f2b8c1e-0a4d-4e6f-9b7a-5c1d2e3f4a5b 3

The id above is only an example. These commands assume you named the server unitley, as the Connect page's setup command does. See Claude Code's guide to MCP prompts (opens in a new tab).

Over the protocolCopy Anchor Link

prompts/list returns each prompt's name, title, description and arguments. prompts/get with a name and its arguments returns the description and one user message holding the filled-in text. Every argument is a string.

A prompt name Unitley does not have, or an argument it cannot use, gets the JSON-RPC error -32602 with a message that says what to fix, such as Invalid arguments for bankroll-check: period: period must be today, week, month or all. An argument a prompt does not list is refused too.

What each prompt doesCopy Anchor Link

weekly-moneyline-valueCopy Anchor Link

Looks for moneyline bets where the agent's own estimate beats FanDuel's price on the coming games, sized to your bankroll.

• Arguments: from and to, each a date such as 2026-10-09 or a date and time such as 2026-10-09T17:00:00Z. Leave both out and get_week_slate covers 6 hours ago to 8 days ahead. A range covers at most 14 days. sport defaults to nfl.
• Steps: read your bankroll, then the games in the range with get_week_slate. For each game, read the moneyline, both teams' injury reports, and the weather when the game is outdoors. Estimate each side's chance, compare it with FanDuel's price using calc_ev (and calc_no_vig_odds where it helps), and keep only a side with a positive edge. Size each pick with calc_kelly_stake and never suggest more.
• The answer: for each pick, the reasoning, the risks, the stake in units and how old the price is. When nothing has value, it says so.

player-prop-parlayCopy Anchor Link

Builds a small player prop parlay for one game, with the correlation risk spelled out. Same-game legs are correlated, so no stake is sized.

• Arguments: gameId (required), from get_week_slate. legs, from 2 to 6, defaults to 3. sport defaults to nfl.
• Steps: read your bankroll, then the game's props with get_player_props, noting each prop's age and passing on its note and priceNote. Read the players' stats, both teams' injury reports and the game's weather. Pick the legs, estimate each one's chance, and price the parlay with calc_parlay, giving each leg's American odds, its chance and the game's id. Since every leg is on one game, the legs are correlated and the combined chance is unreliable: the agent says so and prefers legs that depend on each other least. It does not size the stake with calc_kelly_stake, because Unitley does not size same-game parlays. It leaves the stake to you and says a parlay swings more than a single bet.
• The answer: the reasoning and the risks. When no combination has a positive EV, it says so rather than forcing one.

bankroll-checkCopy Anchor Link

Reviews your bankroll, your results and how close you are to your loss limits.

• Arguments: period: today, week (the last 7 days, the default), month (the last 30 days) or all. See Week.
• Steps: read your bankroll, then your bet log for the period, page by page. Sum up the profit or loss in dollars and units, the win rate, the ROI, the biggest wins and losses, and the money still riding on pending bets.
• The answer: a summary that flags anything near or past a limit. When you are close to a loss limit, it recommends stopping for the period, and it never suggests raising a limit. It logs, settles and saves nothing unless you ask.

See Every tool for the tools these prompts use, and Kelly and stake caps for how weekly-moneyline-value sizes its stakes.