Skip to main content
Glama

Share a League Recap, Power Ranking or Playoff Odds

fantasy_share_league_page

Publish a recap, power ranking or playoff odds page for the league chat; returns its link. ONLY when the user asks for a link or accepts your offer, never unprompted; offer after writing one. League Loom re-reads records and scores; send plain-text notes, no links. No ids are shown; it expires in 30 days. Give the user the share link; the manage link removes the page. Never changes the league.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "fantasy_share_league_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesrecap: scores. power_ranking: your team order. playoff_odds: simulated odds.
weekNoOmit for current.
introNoUp to 600 characters.
sportNoe.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups.
teamsNoExact team names; power_ranking lists every team once, best first. Notes up to 280 characters.
awardsNoUp to 6: title, exact team name, note.
headlineNoUp to 90 characters.
providerNoFantasy platform. Optional: defaults to your connected platform ('sleeper').
league_queryNoA connected league's name/id; omit to auto-pick (primary first). Never ask for ids.
playoff_teamsNoFantrax playoff spots for playoff_odds.
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 / kind / description
      Previous value: -"recap: scores and standings. power_ranking: your order of every team."New value: +"recap: scores. power_ranking: your team order. playoff_odds: simulated odds."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "recap",
      -  "power_ranking"
      -]New value: +[
      +  "recap",
      +  "power_ranking",
      +  "playoff_odds"
      +]
    • addedInput schema / properties / playoff_teams
      Added value: +{
      +  "description": "Fantrax playoff spots for playoff_odds.",
      +  "maximum": 32,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotent=false, destructiveHint=false; the description adds substantial context beyond that: the page expires in 30 days, a separate manage link removes it, no ids are exposed, the service re-reads records/scores so notes must be plain text without links, and the league itself is never modified. The only gap is that it doesn't state whether repeated calls create duplicate pages (idempotency), which the annotations flag as false but the text doesn't operationalize.

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?

Dense and front-loaded: purpose and return value first, then the permission gate, then operational caveats. The semicolon-chained clauses are telegraphic but no sentence is filler; minor cost in readability from packing five distinct rules into two sentences.

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 an 11-parameter publishing tool with no output schema, the description covers the essentials an agent needs: when to call, what it returns (the share link), how long it lives, how to remove it, and that league data is untouched. Remaining details (per-kind required fields, team ordering rules) are fully documented in the schema, so little is missing.

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 coverage is 100% and the schema descriptions already explain kind, week, provider, teams ordering and limits, so the baseline is 3. The description adds only one genuine constraint beyond the schema ("send plain-text notes, no links"), which is useful but narrow.

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?

"Publish a recap, power ranking or playoff odds page for the league chat; returns its link" gives a specific verb (publish), a concrete resource (share page), the three supported kinds, and the return value. An agent can distinguish this from the read-only fantasy_get_* siblings 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?

Explicit gating: "ONLY when the user asks for a link or accepts your offer, never unprompted; offer after writing one." This states both the when and the when-not, plus the sequencing (offer after producing the write-up), 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