Crawlora MCP

pgatour_schedule

Read-only

Get the website-default golf tournament schedule for one PGA Tour context and return the resolved native season (its numeric value and printed label such as 2022-2023), every season choice the site offers, and every tournament with its native ID, name, dates and status. tour selects R (PGA Tour, the default), S (PGA Tour Champions), H (Korn Ferry Tour) or Y (PGA Tour Americas); each tour resolves its own default season, so omit tour to use the website default. IDs stay strings, and no year, category, limit or status filter is exposed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pgatour_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`tour`	No	Optional tour code: R (PGA Tour, the website default), S (PGA Tour Champions), H (Korn Ferry Tour), or Y (PGA Tour Americas). Omit it to use the default R.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real behavior beyond that: the tool resolves a native season (numeric plus printed label like 2022-2023), returns every season choice the site offers, keeps IDs as strings, and offers no filtering so the full tournament list comes back. The implicit upstream-fetch/no-cache nature of an open-world scrape is not mentioned, keeping it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb/resource before the parameter explanation, and the negative-scope clause earns its place by warning about absent filters. It is dense and long for a one-parameter tool, with some repetition of the tour codes already in the schema.

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 single optional-parameter, read-only, open-world tool with an output schema present, nothing needed to call it correctly is missing: defaults, enum meaning, return shape and the absence of filters are all covered. The output schema can carry the detailed structure, so the description does not need to enumerate fields further.

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 'tour' parameter already documents the R/S/H/Y codes with R as default. The description restates that mapping and adds one genuine semantic point — each tour resolves its own default season — but that is marginal added meaning over an already complete 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 opens with a specific verb+resource ('Get the website-default golf tournament schedule') and immediately bounds it to 'one PGA Tour context', which separates it from pgatour_leaderboard, pgatour_players and pgatour_stats without needing their schemas. Scope of the returned data (resolved season, season choices, tournaments) is spelled out.

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 gives clear operational guidance: 'tour' selects one of four circuits, each resolves its own default season, and omitting 'tour' uses the website default R. It also states the negative case ('no year, category, limit or status filter is exposed'), telling the agent it cannot narrow results. It stops short of naming a competing tool for schedule data, so no explicit alternative routing.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?