Skip to main content
Glama

League Loom

by com.leagueloom
OverviewDiscussionsAdmin

Get All My Teams (across every league)

fantasy_get_my_teams
Read-onlyIdempotent

Your personal scoreboard and kickoff check across ALL connected teams. Use for anything plural or cross-league ("my teams", "how am I doing", "my week"; pass sport for "my football teams"); do NOT answer those from one league. ALWAYS render a separate section for EACH team, labeled with team and league; never mix players or points across teams. view=scoreboard (default): your matchups with starter highlights, verified game-progress coverage, and actual score changes when the previous response's comparison_snapshot is passed back. view=kickoff: "am I ready for kickoff", empty slots, injuries, deadlines and replacement options per league. view=summary: lighter standings and totals. Needs a connected profile. For one named league's detail, fantasy_get_my_team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoscoreboard (live scoring), kickoff (lineup readiness) or summary (standings and totals).scoreboard
sportNoOnly this sport, e.g. 'NFL' for 'my football teams'; omit for all.
providerNoOnly this provider; omit for all.
league_queryNoExactly one configured league; omit for all matching teams.
response_formatNo'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload).markdown
comparison_snapshotNoOpaque value from this connection's previous response. Pass it unchanged for actual score changes; never fabricate or show it. Expires after 24 hours; grants no account access.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / comparison_snapshot / description
      Previous value: -"Opaque comparison_snapshot from the previous response to this same connection. Pass unchanged for actual score changes; never fabricate it or show it to the user."New value: +"Opaque value from this connection's previous response. Pass it unchanged for actual score changes; never fabricate or show it. Expires after 24 hours; grants no account access."
    • changedInput schema / properties / league_query / description
      Previous value: -"Optional: exactly one configured league. Omit for all matching teams."New value: +"Exactly one configured league; omit for all matching teams."
    • 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' for 'my football teams'. Omit for ALL sports."New value: +"Only this sport, e.g. 'NFL' for 'my football teams'; omit for all."
    • changedInput schema / properties / view / description
      Previous value: -"scoreboard: compact live scoring per team; kickoff: lineup readiness plus injuries and replacement options; summary: lighter standings and totals."New value: +"scoreboard (live scoring), kickoff (lineup readiness) or summary (standings and totals)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / comparison_snapshot
      Added value: +{
+  "description": "Opaque comparison_snapshot from the previous response to this same connection. Pass unchanged for actual score changes; never fabricate it or show it to the user.",
+  "maxLength": 65536,
+  "type": "string"
+}
    • addedInput schema / properties / league_query
      Added value: +{
+  "description": "Optional: exactly one configured league. Omit for all matching teams.",
+  "type": "string"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "default": "scoreboard",
+  "description": "scoreboard: compact live scoring per team; kickoff: lineup readiness plus injuries and replacement options; summary: lighter standings and totals.",
+  "enum": [
+    "summary",
+    "scoreboard",
+    "kickoff"
+  ],
+  "type": "string"
+}
  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.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond them: comparison_snapshot must be passed back unchanged and expires after 24 hours, requires a connected profile, and the tool renders one section per team without mixing players or points.

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 but front-loaded: scope first, then routing rules, then per-view behavior. Every sentence carries information, though the rendering directives ('ALWAYS render a separate section...') could be trimmed without loss for tool selection.

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?

With no output schema, the description compensates by describing what each view returns (matchups and starter highlights, empty slots and deadlines, lighter standings and totals) plus prerequisites and snapshot reuse. An agent has everything needed to call and interpret it.

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 baseline is 3, but the description adds meaning the schema lacks: sport is exemplified ('NFL' for 'my football teams'), view behavior is spelled out per mode, and comparison_snapshot's opaque/never-fabricate/expiry semantics are clarified.

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 ('personal scoreboard and kickoff check across ALL connected teams') with explicit scope (cross-league, plural). It directly distinguishes itself from the singular sibling fantasy_get_my_team, so an agent can route without opening either 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?

Gives quoted trigger phrases ('my teams', 'how am I doing', 'my week'), an explicit when-not ('do NOT answer those from one league'), and names the alternative for a single named league (fantasy_get_my_team). Routing is unambiguous.

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