Analyzes trade proposals when the user considers trading players, asks 'should I trade X for Y', evaluates a trade offer, or wants to find trade targets. Compares players' stats, evaluates H2H category impact, and considers roster fit. Triggers on: 'trade', 'swap', 'deal', 'give X for Y', 'trade target', 'should I accept', 'trade offer'.
When the user asks about a trade or is evaluating a trade proposal, follow these steps:
Call get_scoring_categories to know all 14 H2H categories and their direction. This is essential — a trade that looks bad in total points might be great for category balance.
Call analyze_trade with the players being given and received (comma-separated names). This gives the baseline stat comparison.
Call get_player_info for each player involved in the trade to get detailed season stats, injury status, and ownership trends.
Call get_my_roster to understand:
If memory tools are available:
get_category_trends to see which categories have been consistently strong or weakget_matchup_history to see if certain categories have been costing you matchupsBuild a category-by-category impact table:
| Category | Direction | Current Strength | Impact | Net Effect |
|---|---|---|---|---|
| HR | Higher wins | STRONG | Lose 5 HR, Gain 2 HR | -3 HR (slight decline) |
| SB | Higher wins | WEAK | Lose 0 SB, Gain 15 SB | +15 SB (big improvement) |
| ERA | Lower wins | AVERAGE | ... | ... |
For each category:
Critical reminders for reverse categories:
Give a clear recommendation:
If the user completes a trade:
save_roster_move with action="TRADE_SEND" for each player given awaysave_roster_move with action="TRADE_RECEIVE" for each player receivedsave_category_trend if the trade significantly changes category projections