Skip to main content
Glama

FantasyTrade Pro

Evaluate a fantasy football trade

evaluate_trade
Read-onlyIdempotent

Judge an NFL fantasy football trade (dynasty or redraft): who wins, how confident the verdict is, the value of every player and pick on each side, the reasons, and what would even it out. Use for "is this trade fair?", "who wins this trade?", "should I accept?". Returns a link that opens the trade in the FantasyTrade Pro calculator.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "you_get": "<you_get>",
      "you_give": "<you_give>"
    },
    "name": "evaluate_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague settings. Omit for the default: 12-team dynasty Superflex, full PPR, 1 QB / 2 RB / 3 WR / 1 TE / 1 Flex (+1 Superflex)
you_getYesWhat the user would receive. Each entry is a player name ("Ja'Marr Chase") or a rookie draft pick: "2027 1st" (add early, mid or late if known, e.g. "early 2027 1st") or an exact slot "2027 1.03"
you_giveYesWhat the user would give up. Each entry is a player name ("Ja'Marr Chase") or a rookie draft pick: "2027 1st" (add early, mid or late if known, e.g. "early 2027 1st") or an exact slot "2027 1.03"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful context that the response includes a link into the FantasyTrade Pro calculator, but says nothing about rate limits, cost, or how unknown players/picks are handled.

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?

One dense sentence front-loads the purpose and then lists the outputs, followed by example trigger phrases. Every clause carries information, though the sentence is long enough that the output list could be broken out for faster scanning.

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?

With only three parameters, a fully documented nested league object, and no output schema, the description is complete: it names the inputs (you_get/you_give), the league context, and the exact shape of the verdict an agent should expect back.

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%, with league settings, PPR, superflex, and the pick-string formats ("early 2027 1st", "2027 1.03") all documented in the schema itself. The description only echoes the two sides of the trade, adding no format or validation meaning beyond what the schema already supplies, so baseline 3 applies.

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?

States a specific verb and resource (judge a fantasy football trade), scopes it to dynasty or redraft, and enumerates the output: winner, confidence, per-player/pick values, reasons, and equalizing moves. That is far more than a restatement of the name and lets an agent distinguish it from valuation siblings like get_player_values.

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?

Provides three concrete user phrasings ("is this trade fair?", "who wins this trade?", "should I accept?") that clearly delimit the use case. It does not, however, say when to prefer suggest_fair_trade_returns or get_player_values instead, so routing against siblings is left to inference.

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