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). |
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. 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.
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.