Skip to main content
Glama

Get Future Draft Picks (pick ownership)

fantasy_get_draft_picks
Read-onlyIdempotent

Who owns each future draft pick now, like Fantrax's Draft Picks page: per team, picks held (acquired ones name their original team) and traded away. Fantrax, Sleeper dynasty.

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_get_draft_picks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoe.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups.
seasonNoDraft year, e.g. 2027.
providerNoFantasy platform. Optional: defaults to your connected platform ('sleeper').
league_idNoOmit when connected. League id (Fantrax also takes the league URL).
team_queryNoOne team (name or id).
league_queryNoA connected league's name/id; omit to auto-pick (primary first). Never ask for ids.
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. Added

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, so safety behavior is covered. The description adds useful data-shape context (acquired picks carry their original team) and a faint platform-support hint ('Fantrax, Sleeper dynasty'), but leaves unclear whether unsupported platforms error or return empty.

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 compact sentences, front-loaded with the core question ('Who owns each future draft pick now'). The trailing fragment 'Fantrax, Sleeper dynasty.' is terse to the point of ambiguity but costs little space.

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?

For a read-only ownership query with no output schema, the description adequately conveys the return shape (per team, held vs traded away, original-team attribution). Gaps remain around behavior with no season given and provider coverage differences on a 7-parameter tool.

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 the schema already explains sport, season, provider, league_id, team_query, league_query and response_format. The description adds no parameter-level meaning such as what season defaults to when omitted, so 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?

States a specific resource and scope: future draft pick ownership, broken into 'per team, picks held ... and traded away', which is clearly distinct from a sibling like fantasy_get_draft that covers actual draft results. The Fantrax 'Draft Picks page' analogy anchors it well. It stops short of naming the sibling it contrasts with.

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?

The trailing 'Fantrax, Sleeper dynasty.' implies the applicable context (dynasty leagues on those platforms) but never says when to pick this over fantasy_get_draft or what happens on ESPN/Yahoo. Usage is implied rather than stated.

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