Search disc golf courses worldwide, find nearby courses, and retrieve course details and updates.
Find disc golf courses within a specified radius (km) of given coordinates.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of nearby courses to return (1-25, default: 10). | |
| latitude | Yes | Latitude in decimal degrees (-90.0 to 90.0). | |
| longitude | Yes | Longitude in decimal degrees (-180.0 to 180.0). | |
| radius_km | No | Search radius in kilometers (0.1 to 100.0 km, default: 25.0). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action without revealing what happens when no courses are found, how results are ordered, whether distances are included, or any rate limiting. This is a significant gap for a read-only query tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero filler. It front-loads the core purpose and avoids redundancy, making it appropriately concise for the information it conveys.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the description is insufficiently complete. It does not mention the return format, result ordering, distance units, error handling, or any edge cases like empty results. An agent would need to guess or call the tool blindly to understand its full behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters (latitude, longitude, radius_km, limit) are already documented in the schema. The description adds minimal extra meaning beyond echoing the 'radius' and 'coordinates' concept, which does not elevate above the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb ('Find') and resource ('disc golf courses') with a specific scoping ('within a specified radius of given coordinates'). It conveys the tool's function distinctly from the sibling tools (e.g., search_courses likely handles name-based search), though it does not explicitly contrast with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to choose this tool over alternatives like search_courses or get_course. It does not mention any exclusions, prerequisites, or typical use cases, leaving the agent to infer when proximity-based search is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Retrieve detailed information for a specific disc golf course by its unique ID or alias.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Stable canonical course identifier or alias (1-256 characters). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. 'Retrieve' explicitly signals a read-only operation, and 'detailed information' hints at the richness of the response. It does not mention permissions or error behavior, but for a simple retrieval these are not critical gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence with no redundant words. It front-loads the action and resource, then specifies the input scope.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one parameter and no output schema, the description is sufficient: an agent knows what to pass and that the result will be detailed. It doesn't describe error cases or edge conditions, but these are not essential for a straightforward get-by-ID operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the 'id' parameter as a canonical identifier or alias, and the description merely echoes this ('by its unique ID or alias') without adding new meaning. Since schema description coverage is 100%, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'retrieve' and names the resource 'disc golf course', making the action and target unambiguous. It also clarifies the selection method (by unique ID or alias), which distinguishes it from the sibling tools like search_courses and find_courses_near.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies that this tool is used when you have a specific course ID or alias, providing the necessary context for selection. However, it does not explicitly name alternatives or state when not to use it, so it misses the top tier of explicit routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Discover recently added or updated disc golf courses with change type and timestamps.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of recent updates to return (1-50, default: 20). | |
| change_type | No | Filter by update type ('added' for new courses, 'updated' for modified courses). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It usefully indicates that results include change type and timestamps and that the operation is a discovery/read action. However, it does not mention ordering, pagination, or the exact shape of the returned course list.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It states the resource, the recency scope, and the key output metadata efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple optional-parameter list tool, the description is mostly complete: it identifies what is returned and the distinguishing update metadata. The main gaps are the lack of explicit sort-order/pagination details and no output schema, but the low complexity keeps these from being critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters are already fully documented. The description loosely aligns 'added or updated' with the change_type enum but adds no new meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Discover') and a specific resource ('recently added or updated disc golf courses'), and mentions the output traits of change type and timestamps. It is clearly distinct from the sibling tools in focus, though it does not explicitly name or contrast those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use is implied: call this when you want recent course additions or modifications. However, there is no explicit guidance about when not to use it or when a sibling like search_courses or find_courses_near would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search for disc golf courses by name, city, country, region, hole count, or features.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1-25, default: 10). | |
| query | No | Text search query for course name, city, or keywords (1-200 characters). | |
| offset | No | Pagination offset (0-1000, default: 0). | |
| region | No | State, province, or region code/name (e.g. 'FL', 'OR', 'England'). | |
| country | No | ISO 3166-1 alpha-2 country code (e.g. 'US', 'GB', 'FI') or country name. | |
| is_free | No | Filter to free-to-play public courses. | |
| is_18_holes | No | Filter to courses with 18 or more holes. | |
| is_pay_to_play | No | Filter to pay-to-play or commercial courses. | |
| is_dog_friendly | No | Filter to dog-friendly courses. | |
| has_multiple_pins | No | Filter to courses with multiple basket/pin positions. | |
| has_multiple_tees | No | Filter to courses with multiple tee pads per hole. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool searches, with no information about result ordering, filter combination behavior, pagination, or any limitations. The read-only nature is implied by the name but not stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. Every word contributes to the core purpose, and it remains easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema documents all 11 parameters well, but the description is thin for a tool with no annotations and no output schema. It does not explain how filters combine, what the response looks like, or how this tool relates to find_courses_near, leaving some gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters are already well documented. The description's list of searchable criteria adds a high-level summary but does not clarify how the boolean feature filters map to 'hole count' or 'features' beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Search') and identifies the resource ('disc golf courses') plus the main search dimensions. It is clear, but it does not explicitly differentiate from the sibling tool find_courses_near.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context about when to use the tool: when searching by name, city, country, region, hole count, or features. However, it does not mention alternatives or exclusions, such as when to prefer find_courses_near for location-based searches.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
find_courses_nearget_courseget_recent_updatessearch_coursesClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Read-only PDGA disc golf data — players, events, courses and season statistics.
Search disc golf discs, compare flight ratings, and find similar alternatives across brands.
Scorecards, tee yardages, USGA ratings and green contour maps for 30,000 golf courses worldwide.
Read-only US golf course, scorecard, equipment, deal, and golf-trip data for AI agents.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: location-based search, attribute-based search, detailed retrieval by ID, and tracking recent updates. There is minimal overlap, and the descriptions clearly differentiate the search methods.
All tools follow a verb_noun pattern, but the verb choice is inconsistent: 'find' for location search, 'search' for attribute search, and 'get' for two other operations. The pattern is readable and predictable, with only minor stylistic variation.
With only 4 tools, the server is tightly scoped to disc golf course discovery and updates. Each tool addresses a distinct need without redundancy, making the count ideal for its purpose.
The surface covers primary workflows: finding courses by location or attributes, retrieving full details, and checking recent changes. Missing are write operations, but for a read-only API the coverage is solid; a minor gap is lack of a direct 'list all courses' endpoint, though search can handle it.
