Crawlora MCP

pgatour_leaderboard

Read-only

Get the website-default golf tournament leaderboard for one PGA Tour context and return its native tournament ID, round and status metadata, every player or scoring row, and the source's native informational rows. tour selects R (PGA Tour, the default), S (PGA Tour Champions), H (Korn Ferry Tour) or Y (PGA Tour Americas); omit it for the website default, which can be a previously published tournament. Player and tournament IDs stay strings with their leading zeroes, and there is no leaderboard selection or paging beyond the website's own default.

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_leaderboard"
  }
}

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.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds genuinely new behavioral context: results track the website's own default rather than a selectable event, IDs are strings that preserve leading zeroes, and the payload mixes scoring rows with the source's non-player informational rows. It stops short of describing auth needs, rate limits, or failure modes when a tour code is invalid.

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?

Front-loaded with the core action and return contents, then the parameter guidance and constraints. It is dense and each clause carries information, though the tour-code list is duplicated from the schema and could be trimmed.

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?

With an output schema present, the description need not explain return shape, yet it still flags the parsing-relevant quirks (string IDs, informational rows). For a zero-required-parameter read tool this is nearly complete; only operational details like failure behavior for an unknown tour code are absent.

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 the description's tour-code mapping (R/S/H/Y) essentially restates what the schema already declares. The only added meaning is the warning that the default may be a stale, previously published tournament — useful, but marginal over a fully documented single parameter.

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?

States a specific verb and resource ('Get the website-default golf tournament leaderboard') plus the exact scope ('one PGA Tour context') and enumerates what the caller receives: tournament ID, round/status metadata, scoring rows, and native informational rows. An agent can distinguish this from a generic golf leaderboard without opening the schema.

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?

Explicitly defines the default behavior ('omit it for the website default') and warns that the default can resolve to a previously published tournament, which is a real usage caveat. It also rules out capabilities an agent might otherwise assume ('no leaderboard selection or paging'), giving clear when-not guidance, though it does not route to any sibling tool.

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?