A
licenseA
qualityB
maintenanceEnables AI agents to search and retrieve detailed information about US golf courses, including course details, tees, climate, and nearby points of interest.
6
470
3
MIT
Pin Seeker
Server Details
Search golf tee times by natural language. Returns GolfNow booking links. Does not book or hold.
- 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.9/5.0
Tool DescriptionsA
Average 4.9/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of ambiguity or confusion between tools.
Naming Consistency5/5
The single tool has a clear, descriptive name ('search_tee_times') that matches its purpose, and with only one tool, naming is inherently consistent.
Tool Count5/5
The server is focused solely on searching golf tee times, and a single search tool is appropriately scoped for that purpose.
Completeness4/5
The tool covers the primary search functionality well, but the server lacks other potential operations (e.g., booking, course details) that might be expected in a golf tee time service, though the description explicitly states it does not book.
Available Tools
1 toolsearch_tee_timesSearch golf tee timesARead-onlyInspect
Search golf tee times, hot deals, and cheapest rounds by city, ZIP, or course name. Use for tee times, booking a round, weekend golf, twilight, or comparing courses nearby. No GolfNow FacilityId needed. Returns GolfNow URLs; does not book, hold, or charge. Ask for a city/ZIP/course and date if missing.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language search, e.g. "Saturday morning near San Francisco for 2" or "Harding Park tomorrow afternoon" | |
| userTimezone | No | IANA timezone of the golfer, e.g. America/Los_Angeles |
Tool Definition Quality
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond the annotations: 'Returns GolfNow URLs; does not book, hold, or charge.' This clarifies the output format and the tool's non-transactional nature. It also states 'No GolfNow FacilityId needed,' which is a useful input requirement detail. These details are consistent with the readOnlyHint and destructiveHint annotations.
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 three sentences long, with each sentence serving a distinct purpose: scope/action, usage context, and limitations/guidance. It is front-loaded with the main purpose and avoids redundant or filler content. No unnecessary details are included.
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?
The tool is relatively simple with only two parameters and no output schema. The description covers all important aspects: what it searches, how to use it, what it returns (GolfNow URLs), what it doesn't do, and how to handle missing inputs. This is complete enough for an agent to invoke the tool correctly in most scenarios.
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 input schema already provides 100% coverage with descriptive parameter text, giving a baseline of 3. The description adds extra meaning by explaining that searches are 'by city, ZIP, or course name,' which clarifies what the 'query' parameter should contain. The 'userTimezone' parameter is sufficiently documented in the schema and doesn't need additional explanation in the description.
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 purpose: 'Search golf tee times, hot deals, and cheapest rounds by city, ZIP, or course name.' It uses a specific action verb ('search') and identifies the exact resource types. It also differentiates itself from booking tools by explicitly noting it 'does not book, hold, or charge.'
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 lists when to use the tool: 'Use for tee times, booking a round, weekend golf, twilight, or comparing courses nearby.' It also provides practical guidance, such as 'Ask for a city/ZIP/course and date if missing,' which helps the agent manage incomplete user requests. The non-booking statement implies a limit on usage, functioning as a when-not.
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
- AlicenseAqualityAmaintenanceManage OpenTable reservations via natural language — find slots, book, cancel, manage favorites, and read your dashboard using your own browser session.13466MIT
- Flicense-qualityDmaintenanceAutomates tennis court bookings on San Francisco Recreation websites using browser automation, with tools to check availability, initiate booking with SMS verification, and complete bookings.9
- Flicense-qualityDmaintenanceProvides tournament event records from the WaterPoker database with intelligent natural language filtering and multiple output formats.