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: "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.

Input Schema

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

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that a connected profile is required, that candidates are options rather than proven upgrades, that coverage warnings should be preserved, and that injury freshness should be verified. It also describes the shape of the returned digest with and without an identified team. The annotations already cover safety and idempotency, and the description adds meaningful operational caveats.

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?

The description is dense but front-loads the core purpose and intended use cases before moving into output detail and caveats. It is longer than strictly necessary, with some repetition around one-league versus all-leagues behavior, but most sentences carry useful routing or behavioral information. It remains readable and well structured.

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?

There is no output schema, so the description must explain return behavior, and it does: identified-team reports include prioritized roster checks, standings, matchups, waiver candidates, FAAB, recent moves, and missing-data warnings; without a team it returns a league overview. Combined with annotations and full schema coverage, this is complete enough for correct 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 coverage is 100%, so the baseline is 3. The description adds useful semantics for league_query by explaining that it narrows the report to one named league and that omitting it includes all matching leagues. It also clarifies that team selection is optional, giving more meaning than the schema alone for those selection parameters.

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 specific verb and resource: a weekly report/digest for one league or all configured leagues. It distinguishes scope clearly and names the sibling tool for a simpler alternative. An agent can tell this apart from generic league-info or team-snapshot tools without opening the schema.

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?

It gives explicit user intents such as 'what needs attention this week', 'weekly rundown/recap', and waiver review. It clarifies when to pass league_query, when team selection is optional, and routes simple single-team snapshots to fantasy_get_my_team. This is strong when-to-use and alternative guidance.

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