Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_golf_schedule

Fetch a golf tour's season schedule, including tournament names, dates, status, purse, and venue, by tour and optional season year.

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 tournament-schedule JSON API. The tour enum accepts pga-tour, pga-european-tours, lpga-tour, champions-tour, and european-tour. Each tournament's id feeds the golf-leaderboard endpoint's tournament parameter.

Input Schema

TableJSON 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.5
    • addedInput schema / properties / tour / enum
      Added value: +[
+  "pga-tour",
+  "pga-european-tours",
+  "lpga-tour",
+  "champions-tour",
+  "european-tour"
+]
  2. Addedv1.14.0

TDQS

A4/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 discloses it returns a schedule from a public API but doesn't mention any limits, pagination, or behavior for unsupported tours. The mutation risk is low (read-only) but not explicitly stated.

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 two sentences, with the primary purpose and return fields front-loaded. The second sentence adds valuable cross-tool context without redundancy.

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?

Given the tool has only two parameters, a clear enum, and no output schema, the description is sufficiently complete. It covers what is returned and how to use the results, though it could mention default season behavior or any exception handling, but that's minor.

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 covers both parameters: `tour` is an enum with the allowed values, and `season` has a description including the default. The description adds the mapping of `tour` values and the relationship of `id` to the leaderboard, providing additional value 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 clearly states it returns a golf tour's tournament schedule for a season, listing the fields (name, dates, status, purse, venue) and the source API. It distinguishes itself from the related leaderboard tool by noting the `id` feeds the leaderboard endpoint.

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 data source and how the output connects to another tool, but doesn't explicitly state when to use this vs. alternatives like yahoo_sports_golf_leaderboard. The context is implied rather than explicit.

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