Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

espn: Get news

espn_get_news
Read-onlyIdempotent

Fetch news articles for a specified sport and league, returning headlines, descriptions, and links so you can stay informed about relevant sports coverage.

Instructions

Get the latest news articles for a sport/league, including headlines, descriptions, and links.

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": {
      "sport": "<sport>",
      "league": "<league>"
    },
    "name": "espn_get_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of articles 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. First observedv1.4.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety and idempotency are covered. The description adds the shape of the response (headlines, descriptions, links), which is useful, but says nothing about result limits, freshness/ordering, or pagination behavior.

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 that names the verb, resource, scope, and returned fields with zero filler. Nothing could be removed without losing information.

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 correctly takes on the burden of describing the return payload (headlines, descriptions, links), and the required sport/league params are clear. It falls short only on ordering/recency guarantees and default result count, which an agent would want for a "latest news" call.

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 sport codes, league codes, limit, and fields are already documented in the schema. The description adds no syntax or format detail beyond identifying that sport/league scope the query, which is the expected baseline when the schema does the work.

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 (get) and resource (latest news articles) scoped to a sport/league, so an agent knows exactly what comes back. It does not, however, distinguish itself from the sibling ncaa_get_news, which reads almost identically.

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?

Usage is only implied by the words "latest news for a sport/league" – there is no explicit statement of when to reach for this vs. ncaa_get_news or the scoreboard/standings siblings. No exclusions or prerequisites are given, leaving the agent to infer the use case.

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