Skip to main content
Glama

yahoo_sports_golf_player_news

Read-only

Fetch one golfer's public Top or Latest story and video news edges by player_url. Latest mode returns an opaque next_cursor; use it with the same player_url to continue.

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": {
      "player_url": "<player_url>"
    },
    "name": "yahoo_sports_golf_player_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoOptional. top or latest; defaults to top.
cursorNoOptional. Opaque Yahoo cursor from a previous latest response.
player_urlYesRequired. Canonical Yahoo Golf player profile URL from the golf-players directory.

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. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond the schema — that the cursor must be paired with the same player_url to continue — but says nothing about result volume, ordering guarantees, or what happens with an invalid/expired cursor.

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, zero filler, with the core fetch behavior front-loaded and the pagination caveat second. Nothing is repeated redundantly or padding the definition.

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 and annotations cover read-only/open-world semantics, so the description needn't explain return shape. For a simple three-parameter read, the description plus schema is nearly sufficient; the only real gap is not pointing to the golf-players sibling as the source of player_url (schema compensates) and no guidance on empty/expired-cursor cases.

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 all three parameters (mode, cursor, player_url) are already documented, including the top/latest values and the cursor's opaque origin. The description restates those semantics in prose without adding format details or edge-case behavior, 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 specific verb ("Fetch") plus the resource ("one golfer's public Top or Latest story and video news edges") and scopes it to a single player via player_url. It is clearly a per-player news feed rather than a directory or profile tool, but it never names the sibling that supplies the player_url (yahoo_sports_golf_players) or contrasts itself with yahoo_sports_player / yahoo_sports_news.

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?

The description explains the mode choice only implicitly (Top vs Latest) and gives concrete continuation guidance for pagination: reuse the cursor with the same player_url. It does not say when a caller should pick this over the general yahoo_sports_player or yahoo_sports_news tools, nor when Latest is preferable to Top.

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.