ESPN Fantasy Football MCP Server

Overview Schema Source Related Servers Discussions Admin

get_head_to_head

Compare two ESPN Fantasy Football teams by retrieving their season head-to-head matchup history, including game results and point totals from each weekly schedule.

Instructions

Get the season head-to-head history between two teams.

Args: team_name_1: First team (name or owner, fuzzy). team_name_2: Second team (name or owner, fuzzy).

Scans each team's weekly schedule for games against the other and reports the results and point totals.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_name_1": "<team_name_1>",
      "team_name_2": "<team_name_2>"
    },
    "name": "get_head_to_head"
  }
}

Input Schema

Name	Required	Description	Default
`team_name_1`	Yes
`team_name_2`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses the mechanism ('scans each team's weekly schedule for games against the other and reports results and point totals'), implying a read-only operation, but says nothing about permissions, season scope limits, or behavior when teams have not met.

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?

The core purpose is front-loaded in a single sentence, followed by a compact Args block and a one-line mechanism note. The Args formatting is slightly verbose relative to the two-parameter schema but nothing is wasted.

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?

An output schema exists, so return-value detail is not required. For a simple two-parameter read tool, the description covers purpose, params, and mechanism adequately, with the main omission being when to pick it over siblings.

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 description coverage is 0%, so the description must compensate, and it does: both params are described as accepting a team name or owner with fuzzy matching. This is meaningful semantics absent from the schema, though format/example detail is still thin.

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: retrieves the season head-to-head history between two teams. This is clearly distinct from around-the-league tools, though it doesn't explicitly differentiate itself from the potentially overlapping compare_teams sibling.

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 guidance on when to use this versus alternatives like compare_teams or get_matchups. The description explains what it returns but gives no conditions, prerequisites, or exclusions to help an agent choose it over a sibling.

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