Skip to main content
Glama

league-loom

by com.leagueloom
OverviewDiscussionsAdmin

Weekly Digest (one team or all your leagues)

fantasy_get_weekly_digest
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportNoOptional: only this sport, e.g. 'NFL'. Omit for ALL sports.
sourcesNoOptional: web sources YOU found while researching this answer (news, injuries, signings). Shown to the user as citations, kept separate from the live league data.
providerNoOptional: only this provider. Omit to aggregate across all.
league_queryNoOptional: one configured league's name or id. Use for a report on just that league; 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) or 'json' (raw payload).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond that: profile requirement, conditional team-based content, missing-data warnings, and an important caveat that waiver candidates are options to review, not proven upgrades. No contradiction with annotations.

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?

Every sentence earns its place: core purpose first, then conditional behavior, usage triggers, parameter guidance, and a caveat. It is compact relative to the tool's complexity and contains no filler.

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?

Given no output schema, the description explains the expected content of both the league-overview and identified-team cases. It also covers prerequisites, exclusions, alternatives, and data-quality caveats, making it complete enough for reliable invocation.

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 description coverage is 100%, so the schema already documents parameters. The description further enriches league_query semantics by explaining when to pass it and the fallback behavior when omitted, which is valuable beyond the schema.

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?

The description states a concrete verb ('return') and resource ('weekly report'), and specifies both the single-league and all-leagues scope. It also differentiates itself by naming fantasy_get_my_team as the simple single-team snapshot alternative.

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?

Explicitly lists triggering user intents ('what needs attention this week', 'my weekly rundown/recap', waiver review), instructs when to pass league_query vs. omit it, and calls out the connected-profile prerequisite. This gives an agent clear selection and invocation criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All league-loom toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources