Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_golf_schedule

Retrieve a golf tour's season schedule from Yahoo Sports, including tournament names, dates, status, purse, and venue for six supported tours.

Instructions

Yahoo Sports golf tournament schedule. Returns a golf tour's tournament schedule for a season (name, dates, status, purse, and venue), from Yahoo Sports' own public sources. The tour enum accepts pga-tour, pga-european-tours, lpga-tour, champions-tour, european-tour, and korn-ferry-tour. Korn Ferry Tour schedule data comes from the Golf page's own server-rendered schedule; the other tours use Yahoo's public tournament-schedule JSON API. Each tournament's id feeds the golf-leaderboard endpoint's tournament parameter.

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": {
      "tour": "<tour>"
    },
    "name": "yahoo_sports_golf_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
tourYesGolf tour key
seasonNo4-digit season year; defaults to the tour's current season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.18
    • changedInput schema / properties / tour / enum
      Previous value: -[
      -  "pga-tour",
      -  "pga-european-tours",
      -  "lpga-tour",
      -  "champions-tour",
      -  "european-tour"
      -]New value: +[
      +  "pga-tour",
      +  "pga-european-tours",
      +  "lpga-tour",
      +  "champions-tour",
      +  "european-tour",
      +  "korn-ferry-tour"
      +]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / tour / enum
      Added value: +[
      +  "pga-tour",
      +  "pga-european-tours",
      +  "lpga-tour",
      +  "champions-tour",
      +  "european-tour"
      +]
  3. Addedv1.14.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and usefully discloses data provenance per tour (server-rendered Golf page vs. Yahoo's public JSON API), the returned fields, and the downstream ID linkage. It does not mention rate limits or error behavior, but for a public read-only schedule endpoint this is solid behavioral context.

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?

The description is front-loaded with the core action and return shape, followed by source details and cross-endpoint linkage. Although it repeats the tour enum from the schema, every sentence contributes either routing context or behavioral detail.

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?

There is no output schema, but the description compensates by listing the key returned fields (name, dates, status, purse, venue) and explaining the tournament ID linkage. It is largely complete for calling the tool correctly, with only minor gaps around failure modes or rate limits.

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%, and both the tour enum and season default are already documented in the schema. The description repeats the enum values, which is useful for routing, but adds no new syntax or semantic constraints beyond what the schema provides.

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 ('Returns') and resource ('a golf tour's tournament schedule for a season') and lists the returned fields. It also names the linked golf-leaderboard endpoint, helping distinguish this schedule tool from leaderboard tools.

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?

Usage context is clear: retrieve a tour's tournament schedule for a season. The description cross-references the golf-leaderboard endpoint for tournament IDs, but does not explicitly state when not to use this tool or name a direct alternative for schedule lookups.

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