Skip to main content
Glama
i-am-david-weinstein

ESPN Fantasy MCP Server

propose_trade

Propose a trade to another team with preview and confirmation steps. First call shows trade details, second call sends the offer and returns a transaction ID for cancellation.

Instructions

Propose a trade with another team. Uses a confirmation pattern: first call (confirm=false) previews the trade, second call (confirm=true) sends it. Returns a transaction ID that can be used to cancel the proposal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentNoOptional message to include with the trade offer
confirmNoIf false (default), returns a preview of the trade. If true, sends the trade proposal.
team_idNoYour team ID (1-based index)
league_idNoESPN League ID (defaults to configured league)
season_yearNoSeason year (defaults to current year)
expiration_daysNoDays until the trade offer expires (default: 7)
send_player_idsNoESPN player IDs you are sending to the other team
receiving_team_idNoThe other team's ID (1-based index)
scoring_period_idNoScoring period for the transaction (defaults to current)
receive_player_idsNoESPN player IDs you want to receive from the other team

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses the two-step behavior (preview vs send) and states that it returns a transaction ID for cancellation. Without annotations, this provides essential behavioral context beyond the input schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no extraneous text. Front-loaded with main purpose, followed by the essential workflow detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description adequately covers the high-level workflow and key return value (transaction ID). For a 10-parameter tool with no required params, this is sufficient for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning by linking the confirm parameter to the overall workflow (preview vs send) and noting the returned transaction ID. This adds value beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool proposes a trade with another team, with a unique confirmation pattern (preview then send). Distinguishes from siblings like accept_trade, decline_trade, and cancel_trade.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains the confirmation pattern for using the tool: first call with confirm=false for preview, second call with confirm=true to send. Implies the workflow but does not exclude using other trade-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/i-am-david-weinstein/espn-fantasy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server