BirdieAPI

Player stats

get_player_stats

Read-onlyIdempotent

Use for a player's season in numbers: results (starts, wins, top tens, cuts, money), scoring average and strokes versus the field, hole scoring from every hole played (birdies and bogeys per round, par 3/4/5 averages) and, for the PGA Tour and Korn Ferry Tour, strokes versus the field by hole type (sg_par3, sg_par4, sg_par5; score-based, not shot data) and, where they exist, driving distance and accuracy, greens in regulation and putts per green. Costs 5 credits.

Input Schema

Name	Required	Description
`league`	No	League. Defaults to golf. One of: golf, lpga, liv, dpwt, kornferry.
`season`	Yes	Season year, e.g. 2025.
`player_id`	Yes	Player id from search_players.

Output Schema

Name	Required	Description	Default
`note`	No
`player`	Yes
`season`	Yes
`results`	Yes
`hole_scoring`	Yes
`ball_striking`	Yes
`published_season`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026

removedOutput schema / properties / espn_season

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / published_season

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "player",
-  "season",
-  "results",
-  "hole_scoring",
-  "ball_striking",
-  "espn_season"
-]New value: +[
+  "player",
+  "season",
+  "results",
+  "hole_scoring",
+  "ball_striking",
+  "published_season"
+]

First observedOct 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a 5-credit cost and coverage limits (sg-by-hole-type only for PGA Tour and Korn Ferry, score-based not shot data, some fields only 'where they exist'). It stops short of stating response shape or empty-result behavior, but it exceeds the annotation baseline.

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?

Front-loaded with "Use for..." and composed of one dense, waste-free sentence; the credit cost is the only trailing element. It is close to a run-on list, which costs a little readability, but every clause carries information.

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?

An output schema exists, so the lengthy return-value inventory is partly redundant with structured data — the description would be better spent on sibling routing. Still, the credit cost and per-league metric availability are context an agent genuinely needs before calling, and nothing critical is missing.

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 player_id, season, and the league enum are fully documented in the schema. The description references league scope for certain metrics but doesn't map that to the league enum values or clarify interactions (e.g. kornferry vs golf), so it adds little beyond the schema. Baseline 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 enumerates exactly what comes back for a player-season: results, scoring average, hole-by-hole scoring, strokes-vs-field by hole type, and where available driving/greens/putts. That is a clear, specific resource statement, but it never distinguishes itself from the overlapping sibling get_player_results or get_player, so an agent must still guess which to call.

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?

"Use for a player's season in numbers" gives an implied context, and the league caveats hint at when certain fields are unavailable. However, there is no explicit when-not guidance and no mention of get_player_results / get_player / get_scorecard as alternatives, despite obvious overlap in return content.

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

All BirdieAPI tools Inspect

Try in Browser