Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pgatour_stats

Retrieve golf statistics overviews by tour with resolved season context and native resource identity, helping you compare public player data while preserving ID formatting.

Instructions

Get the golf statistics overview. 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_stats"
  }
}

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

C2.9/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 behavioral burden. It adds useful return context by mentioning native identity, tour, resolved season context, and leading-zero preservation in player IDs, but it does not disclose pagination, rate limits, auth requirements, or the exact shape of the statistics overview.

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?

The description is front-loaded with its purpose and remains brief across three sentences. The player ID note is useful and earns its place, though 'selected public golf resource' is slightly awkward and could be stated more directly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description gives some return-side context but remains incomplete. It does not clarify what statistics are included, how the resource is selected, or what an agent should expect beyond identity and season metadata.

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?

The schema already documents the single optional 'tour' parameter at 100% coverage, including the enum mappings. The description mentions tour and season context but adds no syntax or selection guidance beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb and resource with 'Get the golf statistics overview,' but the scope is vague: it does not say which statistics or how this differs from siblings such as pgatour_stat_detail or pgatour_stat_options. 'Selected public golf resource' is imprecise and leaves the agent unsure what this tool actually returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the many sibling stats tools, nor any stated exclusions or prerequisites. The description only gives a generic 'get overview' instruction, leaving selection entirely to inference.

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