Skip to main content
Glama

SportStatsAPI

Get golf tournaments

get_golf_tournaments
Read-only

Golf tournaments of the PGA Tour and LPGA by date: course, location, purse, status and the leader or winner. Leaderboards exist for the PGA Tour only. The season money list: get_standings with sport golf.

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

Input Schema

NameRequiredDescriptionDefault
tourNopga or lpga (LPGA: schedule only, no leaderboards)
limitNomax tournaments (default 20, max 100)
offsetNoskip this many tournaments (paging)
seasonNoseason (year)
statusNoscheduled, live, finished, no_results or incomplete
date_toNotournaments starting on or before YYYY-MM-DD
date_fromNotournaments ending on or after YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered; the description adds genuine value by disclosing the coverage asymmetry (LPGA is schedule-only, no leaderboards). It says nothing about paging behavior or how large a result set to expect, which matters for a 7-parameter list 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?

Three short sentences, front-loaded with the resource and returned fields, then the LPGA limitation, then the sibling hand-off. The final sentence is telegraphic ('The season money list: get_standings with sport golf.') but still unambiguous and earns its place.

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?

No output schema exists, so the description usefully enumerates the returned fields and the data-coverage limitation. With all seven parameters documented in the schema, the only meaningful omission is paging/result-size guidance.

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 every parameter including tour, status, and the date bounds is already documented. The description's note that LPGA is schedule-only duplicates the tour parameter's own schema text rather than adding new meaning. Baseline 3 is appropriate when the schema carries the semantics.

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 the resource (golf tournaments on the PGA Tour and LPGA), the organizing axis (date), and the fields returned (course, location, purse, status, leader/winner). It also signals the boundary against get_golf_leaderboard by noting leaderboards exist for the PGA Tour only, so an agent can distinguish the two without opening schemas.

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?

Explicitly routes the season money list use case to get_standings with sport golf, which is a concrete alternative with its selection condition. It does not state when to prefer get_golf_leaderboard over this tool for leaderboard content, leaving that one routing decision to inference.

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