Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

pgatour_stat_detail

Reads a PGA Tour statistics table by native stat ID and returns player and tour-average rows with source season labels, columns, values, and selector menus for stat-year and tournament queries.

Instructions

Read a PGA Tour statistics table. Returns the published player and tour-average rows for a native stat ID. Preserves source season labels, columns, values and selector menus. Use stat options for per-stat years and tournaments; pair query_type with tournament_id. Search, sorting and favorites are not server filters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stat_id": "<stat_id>"
    },
    "name": "pgatour_stat_detail"
  }
}

Input Schema

Name	Required	Description
`tour`	No	Tour
`year`	No	Native year from this stat's options; omission selects the source default
`stat_id`	Yes	Native stat ID from statistics discovery; leading zeroes are significant
`query_type`	No	Native event aggregation; requires tournament_id
`tournament_id`	No	Native tournament ID from this stat and year's options; requires query_type

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that source season labels, columns, values and selector menus are preserved, and warns that 'search, sorting and favorites are not server filters' so filtering must happen client-side. It omits error behavior for invalid stat IDs and any pagination or size expectations.

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?

Four short sentences, each front-loaded with a distinct concern: purpose, return content, selector provenance, parameter coupling, and the client-side filtering caveat. No filler and no repetition of the schema.

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 read-only, five-parameter tool with a fully documented schema and no output schema, the description covers return shape, provenance of IDs, parameter coupling, and the absence of server-side search. Only edge-case behavior for bad IDs or large result sets is left unaddressed.

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%, so all five parameters including both enums are already documented in structured form. The description reinforces the query_type/tournament_id dependency and points to stat options as the source of valid year and tournament values, but adds little syntax or meaning beyond the schema — the baseline of 3 applies.

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 opens with a specific verb and resource ('Read a PGA Tour statistics table') and states what is returned ('published player and tour-average rows for a native stat ID'), which differentiates it from the discovery-oriented pgatour_stats. It stops short of naming the sibling to use for browsing available stats, so an agent must infer that routing.

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 routes prerequisite lookups to the stat options tool ('Use stat options for per-stat years and tournaments') and states the coupling rule 'pair query_type with tournament_id', which is real when-to-use guidance. It gives no when-not guidance or explicit named alternative for the discovery step.

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

Deploy Server