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). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
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.
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.