Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pgatour_stat_options

Retrieve available year, season, tournament, and event-query selectors for a PGA Tour stat table by stat ID before querying statistics.

Instructions

Discover PGA Tour statistics selectors. Returns the native years, season labels, tournaments and event-query types for one statistics table. A year selector refreshes the tournament choices for that season. Stat IDs and category groups come from statistics discovery.

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

Input Schema

NameRequiredDescriptionDefault
tourNoTour
yearNoNative year from this stat's options
stat_idYesNative stat ID from statistics discovery; leading zeroes are significant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the full behavioral burden. It does disclose the chaining behavior (a year selector refreshes tournaments) and the scope limit (one statistics table at a time), but says nothing about whether the call is read-only, how large the response can get, or whether results are cached/rate-limited. Adequate but leaves real gaps for an annotation-free 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?

Four short sentences with no filler, front-loaded with what the tool returns. The dependency facts are packed efficiently into the trailing sentences rather than buried in a preamble.

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 three-parameter discovery tool with no output schema and no annotations, the description covers return contents, scope, and call chaining — everything an agent needs to invoke it correctly and to know what to do with the result.

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%, so the baseline is 3; the schema already explains the tour enum, the native year, and the significance of leading zeroes in stat_id. The description adds only the relational nuance that year drives tournament choices and stat_id selects the table, which is modest value beyond the schema.

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 names a specific verb and resource ('Discover PGA Tour statistics selectors') and enumerates the returned selectors (years, season labels, tournaments, event-query types) scoped to one statistics table. It implicitly distinguishes itself from data-returning siblings like pgatour_stats by framing itself as a discovery/options tool, though it never names a sibling outright.

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?

'Stat IDs and category groups come from statistics discovery' gives an explicit prerequisite for the required stat_id, and 'A year selector refreshes the tournament choices for that season' tells the agent the call is re-invoked per season. There is clear context but no explicit when-not-to-use or named alternative tool.

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