Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

espn: Get scoreboard

espn_get_scoreboard
Read-onlyIdempotent

Fetch live or date-specific scores for any sport and league, returning game status, scores, and basic matchup info on demand.

Instructions

Get live or date-specific scores for a sport/league. Returns current scoreboard with game status, scores, and basic game info.

Input Schema

NameRequiredDescriptionDefault
datesNoDate filter in YYYYMMDD format (e.g. 20240115)
limitNoMaximum number of events to return
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"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
+}
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  2. Changed2 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
  3. First observedv1.2.0

TDQS

A3.6/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 profile is covered. The description adds the return shape ('game status, scores, and basic game info'), but says nothing about pagination, the limit parameter's behavior, or result caps — a modest addition over the 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?

Two sentences, front-loaded with the action and scope, then the return content. No filler or redundancy.

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 summarizes the returned fields, which is the main thing an agent needs. It falls short only on pagination/limit behavior and how the live-vs-date mode is selected.

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 every parameter including dates, limit, fields, sport and league is already documented with examples. The description only alludes to date filtering; it adds no format or interaction detail beyond the schema, so the baseline 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?

The description gives a specific verb and resource ('Get live or date-specific scores for a sport/league') and states what the payload contains. It is clearly a scoreboard/scores tool, though it never explicitly distinguishes itself from near siblings like espn_get_event_summary, espn_get_team_schedule, or espn_get_standings.

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

Usage Guidelines3/5

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

The phrase 'live or date-specific' implies when to reach for it (current games vs. a specific date), but there is no explicit when-not guidance and no mention of alternative ESPN tools for deeper game detail. Usage is implied rather than stated.

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