Skip to main content
Glama

Weekly Digest (one team or all your leagues)

fantasy_get_weekly_digest
Read-onlyIdempotent

Weekly report for ONE league or ALL configured leagues: "what needs attention this week", "my weekly rundown/recap", or waiver review. For identified teams: prioritized roster checks, standings, matchups, position-matched waiver candidates, remaining FAAB where available, recent moves and explicit missing-data warnings. Without an identified team it returns a league overview (standings, matchups, recent activity); team selection is optional. Pass league_query when the user names one league; otherwise all matching leagues are included. Needs a connected profile. Candidates are options to review, not proven upgrades; preserve coverage warnings and verify injury freshness. For a simple single-team snapshot, fantasy_get_my_team.

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

Input Schema

NameRequiredDescriptionDefault
sportNoOnly this sport, e.g. 'NFL'; omit for all.
sourcesNoWeb sources YOU found for this answer (news, injuries, signings), shown as citations apart from the league data.
providerNoOnly this provider; omit for all.
league_queryNoOne configured league's name or id, for a report on just it; omit for all matching leagues.
include_movesNoInclude recent adds/drops/trades per league (false = faster).
include_waiversNoInclude waiver candidates, prioritizing positions with roster alerts (false = faster).
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. Changed7 schema fields changed
    • changedInput schema / properties / league_query / description
      Previous value: -"Optional: one configured league's name or id. Use for a report on just that league; omit for all matching leagues."New value: +"One configured league's name or id, for a report on just it; omit for all matching leagues."
    • 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 / sources / description
      Previous value: -"Optional: web sources YOU found while researching this answer (news, injuries, signings). Shown to the user as citations, kept separate from the live league data."New value: +"Web sources YOU found for this answer (news, injuries, signings), shown as citations apart from the league data."
    • removedInput schema / properties / sources / items / properties / publisher / description
      Removed value: -"Publisher, e.g. 'ESPN'."
    • changedInput schema / properties / sources / items / properties / title / description
      Previous value: -"Headline or short description."New value: +"Headline."
    • 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. Changed6 schema fields changed
    • changedInput schema / properties / include_moves / description
      Previous value: -"Include a compact 'recent moves' line (adds/drops/trades) per league. Set false for a faster digest."New value: +"Include recent adds/drops/trades per league (false = faster)."
    • changedInput schema / properties / include_waivers / description
      Previous value: -"Include a top waiver-wire add per league. Set false for a faster, lighter digest."New value: +"Include waiver candidates, prioritizing positions with roster alerts (false = faster)."
    • addedInput schema / properties / league_query
      Added value: +{
      +  "description": "Optional: one configured league's name or id. Use for a report on just that league; omit for all matching leagues.",
      +  "type": "string"
      +}
    • 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)."
    • addedInput schema / properties / sources
      Added value: +{
      +  "description": "Optional: web sources YOU found while researching this answer (news, injuries, signings). Shown to the user as citations, kept separate from the live league data.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "note": {
      +        "description": "Why it matters here.",
      +        "type": "string"
      +      },
      +      "published": {
      +        "description": "Publish date.",
      +        "type": "string"
      +      },
      +      "publisher": {
      +        "description": "Publisher, e.g. 'ESPN'.",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "Headline or short description.",
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "http(s) link.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "title"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 12,
      +  "type": "array"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the bar is lower — yet the description still adds real context: a connected profile is required, missing-data warnings must be preserved, and include_moves/include_waivers set to false make it faster. It also cautions that waiver candidates are 'options to review, not proven upgrades' and that injury freshness must be verified, which is genuine behavioral guidance not present in structured fields.

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 purpose and scope, then conditions, then the sibling redirect. It is dense and quote-heavy, and the mid-sentence list of report contents is packed, but no sentence is filler and each adds selection or interpretation value.

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?

For a 7-parameter, zero-required tool with no output schema, the description does the necessary work: it describes what the response contains, how the response changes when no team is identified, the auth prerequisite, and the caveats around candidate quality and stale injury data. An agent has enough to call it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by clarifying selection semantics that the schema states more tersely — league_query scopes to one named league while omitting it includes all matching leagues, and the optional-team behavior changes the output shape. It does not restate the sport/provider/enum filters, but the schema handles those adequately.

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 (weekly report/digest) and defines its scope precisely: one league or all configured leagues. It enumerates what the report contains (roster checks, standings, matchups, waiver candidates, FAAB, moves, warnings) and explicitly names the sibling it is not — 'For a simple single-team snapshot, fantasy_get_my_team.'

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

Usage Guidelines5/5

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

Gives concrete user-intent triggers ('what needs attention this week', 'my weekly rundown/recap', waiver review) that map directly to invocation decisions. It states the fallback alternative explicitly and explains when to pass league_query versus omitting it, leaving nothing 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