Skip to main content
Glama

Espn

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Standings

get_standings
Read-onlyIdempotent

League standings / table: win-loss records, win %, games behind (and points/draws for soccer), grouped by conference/division. PREFER for "NBA standings", "Premier League table", "NFL division standings", "who is leading ". Common sport/league pairs: football/nfl, football/college-football, basketball/nba, basketball/wnba, basketball/mens-college-basketball, baseball/mlb, hockey/nhl, soccer/eng.1 (Premier League), soccer/usa.1 (MLS), soccer/esp.1 (La Liga), soccer/uefa.champions (Champions League).

Input Schema

NameRequiredDescriptionDefault
sportYesSport, e.g. 'basketball', 'soccer'.
leagueYesLeague slug, e.g. 'nba', 'eng.1'.
seasonNoOptional 4-digit season year (e.g. 2025). Default = current season.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "league": "nba",
+    "sport": "basketball"
+  },
+  {
+    "league": "eng.1",
+    "season": 2024,
+    "sport": "soccer"
+  }
+]
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare the tool is read-only, idempotent, etc. Description adds context about grouping and soccer-specific fields, but the behavioral burden is largely carried by 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?

Three sentences: purpose, usage examples, common pairs. No unnecessary words, perfectly front-loaded.

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?

No output schema, but description details what the response contains. Missing explicit note that results are grouped by conference/division, but implied. Adequate for a simple tool.

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% with clear descriptions. Description adds value by providing common sport/league pairs and examples, aiding parameter selection 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 clearly states the tool returns league standings/table with specific contents (win-loss, %, games behind, points/draws) and grouping by conference/division. It distinguishes from siblings like get_scoreboard by focusing on standings.

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

Usage Guidelines4/5

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

Provides explicit 'PREFER for' examples (e.g., 'NBA standings', 'Premier League table') and lists common sport/league pairs. Implicitly tells when to use this vs other tools but does not explicitly state exclusions.

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

All Espn 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