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

ESPN Fantasy MCP Server

cancel_waiver

Cancel a pending waiver claim: first preview the cancellation, then confirm to execute. Requires the transaction ID from the original claim.

Instructions

Cancel a pending waiver claim. Uses a confirmation pattern: first call (confirm=false) previews the cancellation, second call (confirm=true) executes it. You need the transaction ID from the original waiver claim to cancel it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoIf false (default), returns a preview of cancellation. If true, executes the waiver claim cancellation.
team_idNoTeam ID (1-based index)
league_idNoESPN League ID (defaults to configured league)
season_yearNoSeason year (defaults to current year)
transaction_idNoTransaction ID from the original waiver claim response
scoring_period_idNoScoring period (week) for transaction (defaults to current period)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses the two-step confirmation pattern to prevent accidental cancellation. It does not detail permissions or irreversible effects, but the preview step mitigates risk.

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?

The description is concise with three sentences: first states purpose, then explains usage pattern, then mentions prerequisite. No extraneous information.

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

Completeness4/5

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

The description covers the tool's purpose, usage pattern, and required inputs. With an output schema present, return values are handled separately. It sufficiently prepares an agent for invocation.

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?

The description adds value beyond the 100% schema coverage by explaining the role of confirm and emphasizing the need for transaction_id. This contextualizes the parameters effectively.

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?

The description clearly states 'Cancel a pending waiver claim' with a specific verb and resource. It distinguishes from siblings like claim_waiver and cancel_trade by focusing on waiver claims.

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?

The description explains the confirmation pattern and the prerequisite of having a transaction ID. It provides clear context on how to use the tool but does not explicitly exclude alternatives or state when not to use.

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