Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

espn_core_call

Access ESPN's core data model to retrieve athletes, statistics, per-event odds, plays, broadcasts, and more. Supply operation and path parameters for sports and leagues.

Instructions

Gateway to the ESPN core data model (sports.core.api.espn.com). The deepest, most canonical surface: athletes + statistics + career logs, per-event odds / win-probabilities / plays / situation / broadcasts / predictor / power-index, per-competitor line-scores + statistics, season teams/coaches/draft/futures, venues, leaders, rankings, franchises and coaches. NOTE the path uses leagues/{league} (plural). Supply operation + path_params (sport, league, plus eventId/competitionId/athleteId/year as needed). Most responses use ESPN's $ref-linked envelope ({count, items:[{$ref}]}); follow the refs for detail. Browse every operation in the espn://core/operations resource.

Returns: (JSON object)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
path_paramsNo
query_paramsNo
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the response format ($ref-linked envelope) but fails to disclose whether the tool is read-only, authentication requirements, rate limits, or any side effects. This is a significant gap for a general-purpose API gateway.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is fairly long and lists many data types, which buries the important usage instructions. It could be more concise and front-loaded with the essential how-to information.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex with many possible operations, but the description omits error handling, authentication, pagination, and comprehensive examples. It mentions the $ref-linked envelope but does not fully explain how to use the API effectively.

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?

The input schema has no parameter descriptions (0% coverage), so the description adds value by explaining that operation and path_params are key, and giving examples of path_params (sport, league, etc.). However, query_params is not addressed, and the information is still somewhat vague.

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 clearly identifies this tool as a gateway to ESPN's core data API, listing many data types it can access. However, it lacks a crisp single-sentence purpose and does not explicitly differentiate this from sibling ESPN tools like espn_cdn_call or espn_standings.

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?

The description provides some usage hints (path structure, parameters) but offers no guidance on when to use this tool versus alternatives. It does not mention exclusions or when not to use it, which is problematic given the large number of sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanielTomaro13/sportsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server