Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pgatour_players

Retrieve a professional golf player directory with tour and resolved season context, including player IDs that retain leading zeroes.

Instructions

Get a professional golf player directory. 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_players"
  }
}

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

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses that the response includes native identity plus tour and 'resolved season context', and flags the genuinely useful quirk that player IDs retain leading zeroes (an operational caveat an agent could otherwise break). However, it says nothing about result volume, whether the whole player list is returned or truncated, pagination, ordering, or what happens when `tour` is omitted — significant gaps for a listing tool with no annotations and no output schema.

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, front-loaded with the purpose, with no filler. The middle sentence ('Returns the selected public golf resource with its native identity...') is jargon-heavy and less informative than its length suggests, but nothing is redundant enough to penalize heavily.

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 one-optional-param read tool with no annotations and no output schema, the description covers purpose and part of the return shape, including the leading-zero ID caveat. It is still incomplete on the things an agent most needs: whether the response is the full player universe or scoped/paginated, default tour behavior, and rough result size.

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% — the single `tour` enum is fully documented in-schema with code meanings (R/S/H/Y). The description adds only a passing reference to 'resolved season context' and does not clarify default behavior when `tour` is omitted or how tour selection interacts with season resolution. Baseline 3 is appropriate since the schema does the parameter work.

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?

States a specific verb and resource: 'Get a professional golf player directory.' An agent can tell this is a read of player entities rather than a stats/leaderboard/schedule tool, matching the pgatour_players name. It stops short of distinguishing itself from other player-directory siblings such as yahoo_sports_golf_players, and 'directory' is slightly ambiguous about whether it is a full listing or a lookup.

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?

Usage is only implied by the word 'directory' — an agent can infer it should call this to enumerate golfers. There is no statement of when to prefer it over sibling player tools, no note on whether the `tour` filter is optional in practice, and no guidance on how to locate a single player given the tool has no name/search parameter.

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