Skip to main content
Glama

Analyze a Trade

fantasy_analyze_trade
Read-onlyIdempotent

Check a proposed trade in ONE league: who rosters each player, league points, projections, age, contract, injury, each team's best projected lineup change (NFL), roster spots needed, and Fantrax/Sleeper pick ownership. Facts, never a verdict; news via fantasy_get_player_data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fantasy_analyze_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
getNoPlayers the user receives.
giveNoPlayers the user sends.
sportNoe.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups.
providerNoFantasy platform. Optional: defaults to your connected platform ('sleeper').
league_idNoOmit when connected. League id (Fantrax also takes the league URL).
team_queryNoYour team's exact id (preferred) or unique name; labels it (your team). Fantrax needs it (no owner data); ESPN/Sleeper auto-detect. Ids: fantasy_get_league_info.
credentialsNoOnly WITHOUT a connected profile: secret_id (Fantrax), espn_s2 + swid (private ESPN), username or user_id (Sleeper discovery). Public ESPN and Sleeper reads need none.
league_queryNoA connected league's name/id; omit to auto-pick (primary first). Never ask for ids.
partner_teamNoOther team's name or id, only to disambiguate.
response_formatNo'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "fantrax",
      -  "espn",
      -  "sleeper"
      -]New value: +[
      +  "fantrax",
      +  "espn",
      +  "sleeper",
      +  "yahoo"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / credentials / additionalProperties
      Previous value: -trueNew value: +{}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's main contribution is the stance: "Facts, never a verdict," telling the agent not to expect or produce a recommendation. That is a genuinely useful behavioral disclosure beyond the structured fields, though return shape and depth of the analysis are not spelled out.

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

Conciseness4/5

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

Two sentences, front-loaded with the verb and scope, with the data list doing real work and the sibling pointer placed last. The compressed comma list is dense but readable; nothing is redundant.

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?

With 10 optional parameters, no output schema, and a nested credentials object, the description usefully compensates by enumerating the analysis dimensions the agent will receive. Minor gaps remain around edge cases such as empty give/get lists or multi-team trades, but the core is covered.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is fully documented in the schema. The description adds only the single-league constraint and the list of league data consulted; it offers no extra syntax or interaction detail beyond what the schema provides, which is the baseline case.

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?

"Check a proposed trade in ONE league" is a specific verb and resource, immediately scoped, and the enumeration of facts returned (rosters, points, projections, age, contract, injury, lineup impact, pick ownership) makes the purpose concrete. It also distinguishes itself from fantasy_get_player_data by routing news questions there.

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?

Usage context is clear (evaluating a proposed trade) and an explicit alternative is named for news lookups. It stops short of saying when not to use it, e.g. for waiver adds or multi-league comparisons, and the "ONE league" emphasis hints at a boundary without stating it as guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources