Skip to main content
Glama

FantasyTrade Pro

Get player trade values

get_player_values
Read-onlyIdempotent

Current trade value of one or more NFL players for a fantasy football league: value on a 0 to 10,000 scale with a likely range, overall and position rank, projected points per game and the change over the last week. Use to compare players or answer "what is X worth?".

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": {
      "players": "<players>"
    },
    "name": "get_player_values"
  }
}

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)
playersYesPlayer names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower. The description still adds real value by disclosing the shape of the response — a 0-10,000 scale, likely range, overall and position rank, projected points per game, and one-week change — which is important since no output schema exists. It stops short of noting freshness or whether unknown/invalid player names error out.

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, zero filler, and the core capability is front-loaded before the usage hint. The enumeration of return fields is compact and readable rather than a bulleted dump.

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 nested league settings fully documented in schema and no output schema, the description adequately covers what an agent needs: what the numbers mean and the scale they sit on. Minor gaps remain around input validation for unrecognized player names and whether values are refreshed in-season.

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 every league sub-field (ppr, teams, format, pass_td, superflex, te_premium) documented inline including defaults and omitted-league behavior, so the schema does the heavy lifting. The description mentions 'for a fantasy football league' but never states that league settings materially change the returned values, leaving that inference to the schema. Baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource: 'Current trade value of one or more NFL players for a fantasy football league,' and enumerates what the value comprises. It doesn't explicitly name siblings such as evaluate_trade or get_rankings, so differentiation relies on the phrase 'Use to compare players or answer "what is X worth?"' rather than a direct contrast.

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

Usage Guidelines3/5

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

'Use to compare players or answer "what is X worth?"' gives an intended use case, which is better than nothing. However, it offers no when-not guidance and no routing against evaluate_trade, suggest_fair_trade_returns, or get_rankings — an agent must infer that this tool returns raw values while the siblings perform trade analysis.

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