Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

espn: Get athlete

espn_get_athlete
Read-onlyIdempotent

Retrieve an athlete's bio, stats, and career history by sport, league, and ESPN athlete ID for player research and comparison.

Instructions

Get information about a specific athlete, including bio, stats, and career history.

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"
athlete_idYesESPN athlete 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.2/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 that the response contains bio, stats, and career history, which is useful return-shape context, but says nothing about rate limits, auth, or data freshness.

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?

A single efficient sentence with the resource leading and the returned content trailing. No filler, though it is arguably under-specified rather than maximally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 partially compensates by naming the return categories, and annotations cover the safety profile. But it omits why sports/league are required and how the 'fields' projection parameter behaves, leaving gaps for a 4-parameter lookup tool.

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%, with sport, league, athlete_id, and fields all documented in the schema itself. The description adds no syntax, format, or relationship detail (e.g. that sport/league scope the athlete lookup), so 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?

States a clear verb+resource ('Get information about a specific athlete') and enumerates the content categories (bio, stats, career history). However, with siblings like mlb_get_player, nhl_get_player, and sportsdb_get_player_details, it never signals that this is the cross-sport ESPN source, so sibling differentiation is missing.

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?

No statement of when to choose this over the many player/athlete siblings (mlb_get_player, nhl_get_player, opendota_get_player, sportsdb_get_player_details). No exclusions, prerequisites, or context cues are given; the agent must infer usage entirely from the name.

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