Skip to main content
Glama

SportStatsAPI

Get golf player

get_golf_player
Read-only

A golfer's profile (country, birth date and place, PGA Tour rank) and season results from our leaderboards with events, wins, top 10s, cuts made and earnings (player_id); or find golfers by name.

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": "get_golf_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNopart of a golfer's name, to find the id
seasonNoseason of the results (default: the latest)
player_idNoplayer code (or number) from a leaderboard: profile and the season's results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / player_id / description
      Previous value: -"player id from a leaderboard: profile and the season's results"New value: +"player code (or number) from a leaderboard: profile and the season's results"
    • changedInput schema / properties / player_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the useful behavioral detail that results include season aggregates (wins, top 10s, cuts made, earnings) and that lookups can be by name or id. It does not disclose what happens when a name matches multiple golfers, whether name-only lookups return just ids, or what data comes back when season is omitted beyond the schema's 'default: the latest'. The idempotentHint=false is left unexplained.

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?

It is a single dense sentence with no filler, and the primary payload (profile fields) is front-loaded before the alternative name-search mode. The heavy parenthetical nesting ('country, birth date and place, PGA Tour rank') makes it slightly harder to parse but every clause carries content.

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?

With no output schema, the description does a reasonable job enumerating return fields, which is the main thing an agent needs. However, for a dual-mode tool with three optional parameters, it omits what the name path actually returns (ids vs. profiles), disambiguation behavior, and the effect of combining name with player_id or season.

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 all three parameters are already documented, and the description largely restates them. It does add slight framing by pairing player_id with 'profile and the season's results' and by tying season to those results, but adds no format, range, or matching-behavior detail (e.g., partial-name semantics, multiple matches, interplay of name+player_id).

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 resource (golfer profile) and enumerates the fields returned (country, birth date/place, PGA Tour rank, events, wins, top 10s, cuts made, earnings), and it distinguishes two access modes: player_id for a profile+season results, or name to find golfers. It is clearly a golf-player lookup rather than a leaderboard/tournament tool, though it never explicitly contrasts itself with the sibling get_player or get_golf_leaderboard.

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 implied rather than stated: the parenthetical '(player_id)' attaches to the season-results output, and 'or find golfers by name' hints at a resolve-then-fetch workflow. There is no explicit when-to-use/when-not, no guidance on choosing between name and player_id, and no routing to the sibling leaderboard or generic player tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources