Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

pgatour_players

Read-only

List the professional golf player directory for one PGA Tour context and return every source directory entry with its native player ID, display name, country, tour and active state. tour selects R (PGA Tour, the default), S (PGA Tour Champions), H (Korn Ferry Tour) or Y (PGA Tour Americas). Player IDs such as 01001 stay strings with significant leading zeroes, the directory includes inactive players, and there is no paging, search or roster deduplication across tours.

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

Input Schema

NameRequiredDescriptionDefault
tourNoOptional 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

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful behavior beyond them: the directory includes inactive players, IDs remain strings with significant leading zeroes, and there is no paging, search or deduplication across tours. It still omits typical size/volume and whether the full roster is returned in one response, but against the annotation baseline this is solid added context.

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?

Two sentences, front-loaded with the action and return shape, followed by a dense but purposeful caveat sentence. Every clause (ID string preservation, inactive players, no paging/search/dedup) carries information an agent would otherwise get wrong, though the second sentence is packed and could be broken up.

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?

Complete for a zero-required-parameter, single-parameter listing tool with an output schema that documents return values. Default handling, enum meanings and the no-pagination/no-search constraints are all covered, leaving only response-size expectations unstated.

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% and the single tour parameter's schema description already lists all four codes and the R default; the description restates the same mapping without adding syntax or edge-case meaning. Baseline 3 applies since the schema carries the semantics.

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 ("List the professional golf player directory") plus the scope and the exact fields returned (native player ID, display name, country, tour, active state). The word "directory" clearly separates it from sibling tools like pgatour_leaderboard and pgatour_stats without needing to name them.

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?

Explains the selection logic for the only parameter (tour R/S/H/Y with R as default when omitted) and sets expectations that there is no paging, search or cross-tour deduplication, which implicitly steers an agent away from expecting search behavior. It stops short of explicitly naming an alternative tool for filtered or searched roster lookups.

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

All Crawlora MCP toolsInspect
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