Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

espn: Get event summary

espn_get_event_summary
Read-onlyIdempotent

Retrieve play-by-play, box score, leaders, and game info for a specific ESPN event to analyze match details by sport, league, and event ID.

Instructions

Get a detailed summary of a specific event/game, including play-by-play, box score, leaders, and game info.

Input Schema

NameRequiredDescriptionDefault
sportYesSport code, e.g. "football", "basketball", "baseball", "hockey", "soccer", "mma", "golf", "tennis", "racing"
fieldsNoKeys to keep (comma-separated).
leagueYesLeague code, e.g. "nfl", "nba", "mlb", "nhl", "wnba", "college-football", "mens-college-basketball", "eng.1", "usa.1", "ufc", "pga", "atp", "f1"
event_idYesESPN event ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and repeatability profile is covered. The description adds a content inventory of the response (play-by-play, box-score, leaders, game info), which is genuinely useful given there is no output schema, but says nothing about availability before/after an event or rate/coverage limits.

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?

A single front-loaded sentence with the verb, scope and content list; no filler and nothing an agent must skip past.

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?

With no output schema, the description usefully enumerates what the summary contains, and the schema plus annotations cover parameters and safety. It stops short of covering edge cases such as events not yet started or sports where play-by-play is unavailable.

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 description coverage is 100%, so the schema already documents sport, league, event_id and the fields projection. The description adds no syntax, format or default guidance beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get a detailed summary of a specific event/game) and enumerates the payload's contents (play-by-play, box score, leaders, game info). This is well beyond a tautology, but it never names the sibling it competes with — espn_get_scoreboard or nhl_get_game_landing — so an agent must infer the distinction from the schemas.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says this requires a completed or in-progress event, nothing contrasts it with espn_get_scoreboard or the per-league game tools, and no prerequisites are stated. Usage can only be inferred from the required event_id parameter.

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

Deploy Server

Other Tools