A
license-
qualityD
maintenanceOfficial MCP server for exerciseapi.dev — give your AI coding agent direct access to 2,198+ vetted exercises across 12 categories.
26
1
MIT
PGA Golf
by com.pga
Server Details
PGA's official MCP Server for all things golf-related. Find a coach, play golf, improve your game.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.5/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool serves a distinct step in the booking workflow: search for coaches, check availability, and book a lesson. There is no overlap between the tools, and the descriptions clearly delineate when to use each.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: search_golf_coaches, get_golf_coach_availability, book_golf_lesson. The verbs and nouns are specific and matching, making the API predictable.
Tool Count5/5
Three tools is well-scoped for a focused golf lesson booking server. Each tool earns its place and together they form a complete search-availability-booking flow without unnecessary bulk.
Completeness4/5
The core lifecycle of searching, checking availability, and booking is fully covered. A minor gap is the lack of cancellation or rescheduling tools, but these may be handled outside the server's stated purpose.
Available Tools
3 toolsbook_golf_lessonBook Golf LessonAInspect
Request to book a golf lesson for a specific coach's offering.
offeringIdis an internal identifier; never show or mention it to the user.A continuation URL will be returned that you can direct the user to after calling this tool.
If the offering was booked automatically (e.g., free lesson or no prepayment required), the confirmation code will also be included.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| student | Yes | ||
| offeringId | Yes | Internal offering record ID to book a lesson for. Never display or mention this identifier to the user. | |
| startDateTime | Yes | The start date and time of the lesson in ISO 8601 format. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| lesson | No | Confirmation details for the booked lesson (if booked successfully). |
| message | Yes | A message describing the outcome of the booking. |
| continuationUrl | No | The URL to continue the booking flow after calling this tool. |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond the annotations: it discloses that a continuation URL is returned, that a confirmation code may be included for automatic bookings, and that offeringId must never be shown to the user. These details help the agent understand the response flow and handle sensitive identifiers correctly. The annotations only indicate non-readonly, so this extra context is valuable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured, with a clear opening statement followed by three relevant bullet points. Every sentence adds value, and there is no redundant or filler content.
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?
Given the tool's complexity (booking with different student types, internal IDs, and follow-up URLs), the description covers key aspects: the internal ID privacy rule, the continuation URL, and conditional confirmation codes. The existence of an output schema reduces the need to explain return values. It could mention prerequisites like checking availability, but the sibling tools imply that workflow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers most parameter meanings (student details, startDateTime format, offeringId as internal record ID). The description adds crucial usage semantics by emphasizing that offeringId is internal and must never be displayed or mentioned to the user, and by clarifying that a continuation URL will be returned. This goes beyond schema descriptions and helps with correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: requesting to book a golf lesson for a specific coach's offering. It uses a specific verb and resource, and the context of booking a lesson distinguishes it from sibling tools like get_golf_coach_availability and search_golf_coaches.
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?
The description provides clear context for when to use the tool—when booking a lesson for a specific offering—and what to do after calling it (direct the user to the continuation URL). It does not explicitly mention alternatives or exclusions, but the purpose is unambiguous enough that an agent can select it appropriately alongside the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_golf_coach_availabilityGet Golf Coach AvailabilityARead-onlyInspect
Retrieve offering details and available lesson times for one specific coach.
Use this when the user asks for schedule, openings, or available times for a known coach.
If the user has not selected a coach yet, call search_golf_coaches first.
Coach slug and offering id values are internal identifiers and must never be shown or mentioned to the user.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Coach slug from a pga.com profile URL or prior `search_golf_coaches` results (e.g., `anthonyvitale`). Internal-only value; never display or mention it to the user. | |
| offeringId | No | Optional offering ID to scope availability to a single offering. Use this when the user has already selected an offering. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| coach | Yes |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only and non-destructive, so the agent knows it is safe. The description adds valuable context beyond annotations, especially the rule that internal identifiers 'must never be shown or mentioned to the user,' which is critical for proper invocation and response handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences, each earning its place: purpose, use case, alternative pre-step, and a privacy constraint. No fluff or repetition, and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the availability of an output schema and annotations covering safety and side effects, the description is complete enough. It covers when to use, the necessary pre-step, and the critical internal-ID privacy rule, leaving no major gaps for a 2-parameter tool.
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%, with both `slug` and `offeringId` already well-documented. The description reinforces the internal-only nature and optional offering scope, but adds little beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Retrieve offering details and available lesson times for one specific coach,' which is a specific verb+resource combination. It distinguishes itself from siblings by focusing on a single coach's availability rather than searching or booking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool ('when the user asks for schedule, openings, or available times for a known coach') and provides an alternative when the coach is unknown, 'call `search_golf_coaches` first.' This is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_golf_coachesSearch Golf CoachesARead-onlyInspect
Search for qualified PGA golf coaches listed on pga.com/coach in the specified location (required).
Use this tool when the user asks to find, browse, or compare coaches in a location.
If the user asks for availability for a specific coach, use get_golf_coach_availability instead.
Internal record identifiers (for example coach slug and offering id) are for tool calls only and must never be shown or mentioned to the user.
Search results include the coach's profile information, offerings, and pricing.
Results are ordered by proximity to the search location, so list them to the user in this order.
Results are paginated, so use the pagination cursor provided at the end of the response to retrieve the next page of results.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| searchRadius | No | Search radius in miles from `searchLocation`. Use 25 by default unless the user requests a different radius. | |
| searchLocation | Yes | Required location used to find nearby coaches. Accepts city/state, ZIP code, full address, or latitude/longitude coordinates. | |
| paginationCursor | No | Pagination cursor from a prior `search_golf_coaches` response. Use only when fetching additional pages of the same search. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| coaches | Yes | |
| endCursor | Yes | |
| hasNextPage | Yes |
Tool Definition Quality
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses that results are ordered by proximity, paginated with a cursor, and include coach profile info, offerings, and pricing. It also states a critical policy: internal record identifiers must never be shown to the user. These behavioral disclosures go well beyond the annotation.
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?
The description is well-structured with a clear opening sentence, usage guidance, and bulleted behavioral notes. It is slightly longer than strictly necessary, but every sentence adds value. The front-loaded purpose makes it easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the search tool's moderate complexity, the description covers the main use case, result ordering, pagination, result contents, and the ID-privacy restriction. The output schema exists and handles return-value detail, so the description is sufficiently complete.
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?
The input schema has 100% parameter description coverage, so the description need not add much. It reinforces that searchRadius defaults to 25 and paginationCursor is only for additional pages, but this is already in the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Search for qualified PGA golf coaches listed on pga.com/coach in the specified location.' It clearly distinguishes from the sibling tool `get_golf_coach_availability` by naming it explicitly as the alternative for availability queries. This makes the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states exactly when to use: 'when the user asks to find, browse, or compare coaches in a location.' It also provides an explicit when-not: 'If the user asks for availability... use get_golf_coach_availability instead.' This exceeds the baseline by naming the alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
QA Touch MCP Serverofficial
Alicense-qualityBmaintenanceOfficial MCP server for QA Touch, enabling AI assistants to manage test cases, defects, test runs, and more via natural language.61MIT- AlicenseAqualityBmaintenanceOfficial MCP Server for Indian Stock Market (NSE & BSE) equities, futures context, and option chains.6MIT
- AlicenseAqualityBmaintenanceOfficial MCP server for Scorezilla (leaderboards for games). Your AI coding assistant can bootstrap a leaderboard, inspect games and boards, read top-N standings, and paste ready-to-run SDK integration code — without leaving the editor.6321MIT