Skip to main content
Glama

yahoo_sports_news

Read-only

Fetch recent Yahoo Sports news articles for one league using its supported league key. Use yahoo_sports_scoreboard for games and scores, or yahoo_sports_game for one game's details.

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

Input Schema

NameRequiredDescriptionDefault
leagueYesRequired. Yahoo league key from yahoo-sports-leagues.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / league / description
      Previous value: -"Required. League key. One of nfl, nba, wnba, mlb, nhl, college-football."New value: +"Required. Yahoo league key from yahoo-sports-leagues."
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds that results are recent articles for one league. It does not disclose additional behavior such as rate limits, authentication requirements, or result freshness/ordering beyond 'recent', so it adds only modest value beyond 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 primary action and immediately followed by sibling routing. Every sentence earns its place with no redundant restatement of the name or title.

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

Completeness5/5

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

For a simple one-parameter read-only tool with full schema coverage, annotations, and an output schema, the description provides enough context to invoke it correctly. It also names the two most likely alternative tools for games and scores.

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 coverage is 100%, and the single league parameter is fully documented in the schema as a Yahoo league key from yahoo-sports-leagues. The description reinforces that the key must be supported, but does not add format details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: fetching recent Yahoo Sports news articles, scoped to one league. It explicitly distinguishes this tool from yahoo_sports_scoreboard and yahoo_sports_game, so an agent can select it without opening sibling schemas.

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

Usage Guidelines4/5

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

It clearly routes game and score needs to yahoo_sports_scoreboard and single-game detail needs to yahoo_sports_game. However, it does not address other potentially competing news tools such as yahoo_sports_more_news or yahoo_sports_topic_news, so the guidance is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.