Skip to main content
Glama

FantasyTrade Pro

Get fantasy football rankings

get_rankings
Read-onlyIdempotent

Fantasy football trade-value rankings for a league format (dynasty or redraft, Superflex or 1QB), for all positions or one of QB, RB, WR, TE. Returns rank, value and one-week change, 25 players at a time by default.

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": "get_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many players to return
leagueNoLeague settings. Omit for the default: 12-team dynasty Superflex, full PPR, 1 QB / 2 RB / 3 WR / 1 TE / 1 Flex (+1 Superflex)
offsetNoSkip this many from the top (for the next page)
positionNoOnly this position. Omit for all positions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavior beyond that: the exact return payload (rank, value, one-week change) and the default page size of 25. It does not describe ordering guarantees, how rankings change between calls, or rate limits.

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 tight sentences, front-loaded with the resource and scope, then the return shape and pagination default. No filler. A slightly stronger version would name the sibling tools instead of spending the second sentence restating schema defaults.

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 no output schema, the description correctly compensates by naming the returned fields and page size, and the nested league-object defaults are fully specified in the schema. Combined with annotations covering the read-only profile, an agent has enough to call this correctly; only sibling disambiguation is missing.

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 including the nested league object is already documented. The description largely restates that content (the position enum values, the two league formats, the 25-player default) rather than adding new semantics such as what the numeric value scale means. Baseline 3 is appropriate.

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?

States a specific resource and scope: trade-value rankings, with the league-format dimensions (dynasty/redraft, Superflex/1QB) and position filter spelled out. An agent can tell what it returns (rank, value, one-week change). It stops short of differentiating itself from siblings like get_player_values or get_rookie_pick_values, which a reader still has to infer.

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?

Usage is implied rather than stated: the format/position framing suggests when the tool fits, and the 25-per-page default hints at paging through results. There is no explicit when-to-use, no prerequisite notes, and no mention of when an agent should prefer get_player_values or evaluate_trade instead.

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