Skip to main content
Glama
opengolfapi

OpenGolfAPI MCP Server

Official
by opengolfapi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SENTRY_DSNNoOptional Sentry DSN for sending errors to your own Sentry instance. When unset, SDK is a no-op.
OPENGOLFAPI_KEYNoOptional API key for higher rate limits. Get a free key at https://courses.opengolfapi.org/api-keys

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_coursesA

Search golf courses by name, state, or location. Returns full course info. ODbL licensed data from OpenGolfAPI.

get_courseA

Get detailed golf course info including full scorecard with par and handicap index per hole. ODbL licensed.

get_teesA

Get all tee sets for a course including ratings, slopes, and yardages per tee. ODbL licensed.

get_climateB

Get monthly climate normals for a course (temperature, precipitation, playability). ODbL licensed.

get_nearbyA

Get nearby points of interest for a course (hotels, restaurants, airports) within ~20 miles. ODbL licensed.

aboutA

Information about OpenGolfAPI: dataset size, license, how to contribute, how to contact the maintainers. Useful when an AI agent or user wants to know who built this and how to reach them.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: about for metadata, get_climate for weather, get_course for details, get_nearby for POIs, get_tees for tee sets, and search_courses for searching. No overlap or ambiguity.

Naming Consistency4/5

Most tools follow a consistent 'get_' prefix for data retrieval (get_climate, get_course, get_nearby, get_tees), along with search_courses and about. While about deviates, it is a common convention for info commands, so only minor inconsistency.

Tool Count5/5

Six tools is well-scoped for a golf course data API. Each tool covers a key aspect (search, course info, tee sets, climate, POIs, metadata) without being overwhelming or insufficient.

Completeness4/5

The set covers the main data retrieval operations for golf courses: search, details, tees, climate, and nearby points. Minor gaps like course reviews or booking are absent, but the core domain is well-served.

Maintenance

ActivitySlowing
ResponsivenessNo issues