Skip to main content
Glama

Get My Players (exposure across every league)

fantasy_get_my_players
Read-onlyIdempotent

YOUR EXPOSURE MAP: every player you roster across ALL configured leagues and providers, ranked by how many of your teams hold them (matched across platforms). For "who do I have everywhere", "players on several of my teams", "my exposure", "if X gets hurt how many of my teams does it hit". Needs a connected profile.

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

Input Schema

NameRequiredDescriptionDefault
sportNoOnly this sport, e.g. 'NFL'; omit for all.
providerNoOnly this provider; omit for all.
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. Changed3 schema fields changed
    • changedInput schema / properties / provider / description
      Previous value: -"Optional: only this provider. Omit to aggregate across all."New value: +"Only this provider; omit for all."
    • changedInput schema / properties / response_format / description
      Previous value: -"'markdown' (default) or 'json' (raw payload)."New value: +"'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload)."
    • changedInput schema / properties / sport / description
      Previous value: -"Optional: only this sport, e.g. 'NFL'. Omit for ALL sports."New value: +"Only this sport, e.g. 'NFL'; omit for all."
  3. Changed2 schema fields changed
    • changedInput schema / properties / provider / description
      Previous value: -"Optional: only this provider. Omit to aggregate across Fantrax, ESPN, and Sleeper."New value: +"Optional: only this provider. Omit to aggregate across all."
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: 'markdown' (default, human-readable) or 'json' (raw upstream payload)."New value: +"'markdown' (default) or 'json' (raw payload)."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety bar is low. Beyond that the description discloses the aggregation and ranking behavior (ordered by number of your teams holding a player), cross-platform identity matching, and the connected-profile precondition — all genuinely useful context not carried by annotations.

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?

Front-loaded with the core meaning in the first clause, then the query intents, then the prerequisite — no filler sentences. The quoted-phrase list is slightly repetitive but each phrase maps to a distinct intent an agent might match against, so it earns its 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?

With zero required parameters, no output schema, and annotations covering the safety profile, the description supplies the essential framing: scope, ranking semantics, cross-platform matching, and the profile requirement. It does not describe what a returned row contains (counts, per-team breakdown), a minor gap for a tool without an output schema.

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 documents sport, provider, and response_format semantics including enums and the default. The description adds only the implicit 'omit for all' scoping notion, which aligns with but does not extend the schema; 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 resource and operation: every rostered player across all configured leagues and providers, ranked by team-hold count with cross-platform matching. The 'exposure map' framing plus 'across ALL configured leagues' cleanly separates it from single-team siblings like fantasy_get_my_team and fantasy_get_my_teams.

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 concrete when-to-use triggers in the user's own words ('who do I have everywhere', 'players on several of my teams', 'if X gets hurt how many of my teams does it hit') plus the prerequisite 'Needs a connected profile.' It stops short of naming an alternative tool or stating when-not-to-use this one, so it is clear context without explicit routing.

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