Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pgatour_leaderboard

Fetches the website-default golf leaderboard for a selected tour, returning clean JSON with native identities, resolved season context, and player IDs that preserve leading zeroes.

Instructions

Get the website-default golf leaderboard. Returns the selected public golf resource with its native identity, tour and resolved season context. Player IDs retain significant leading zeroes.

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

NameRequiredDescriptionDefault
tourNoR: PGA Tour; S: Champions; H: Korn Ferry; Y: Americas

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose useful behavior: the result carries native identity, tour and resolved season context, and player IDs retain leading zeroes (a real data gotcha worth flagging). It does not say whether the leaderboard is live/in-progress, how the default event is chosen, whether data can be stale, or anything about auth or limits, so it is only partly transparent for an unannotated tool.

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?

Three short sentences with the core purpose front-loaded and no filler. The middle sentence ("selected public golf resource with its native identity") is slightly jargon-heavy and vaguer than the rest, but nothing is truly wasted.

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?

For a one-optional-parameter read tool with no output schema, the description covers the essential shape: what it returns, the tour/season context, and the leading-zero caveat. The remaining gap is which event the default leaderboard corresponds to, but overall it is adequate for the tool's simplicity.

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 sole parameter is a fully enumerated tour code, so the schema already does the work. The description mentions "tour" only as a returned field and adds no argument-level meaning such as default behavior when tour is omitted.

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?

The description gives a specific verb and resource ("Get the website-default golf leaderboard") and the qualifier "website-default" distinguishes it from a generic leaderboard. It stops short of naming a specific alternative such as yahoo_sports_golf_leaderboard, so sibling differentiation is implied rather than stated.

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 phrase "website-default" implies when to reach for this tool (when you want the PGA Tour site's default view rather than a provider-specific one), but there is no explicit when-to-use or when-not-to-use guidance and no alternative is named. Usage must be inferred from the wording.

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