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?
No annotations are provided, so the description carries the full disclosure burden. It reveals that results include change type and timestamps, which is useful, but it doesn't explicitly state that the operation is read-only, how results are ordered, or the exact return structure.
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?
A single 12-word sentence that conveys the core purpose and key returned attributes. It is front-loaded with the action and resource, with zero filler or redundancy.
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 list tool with two optional parameters and no required arguments, the description covers the core use case and indicates output fields. It doesn't specify ordering or exact return shape, but the simplicity and full schema documentation make the definition nearly complete.
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 baseline is 3. The description mentions 'change type', consistent with the change_type parameter, but adds no semantics or constraints beyond what the schema already documents for limit and change_type.
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?
States a specific verb ('Discover'), resource ('recently added or updated disc golf courses'), and key output fields ('change type and timestamps'). The recency focus clearly distinguishes it from sibling tools like find_courses_near, get_course, and search_courses.
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 implies a clear use case (checking recent course changes), but it doesn't explicitly state when to choose this tool over siblings or mention alternatives. An agent must infer the boundary from the tool's name and description without explicit comparison.
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 targets a distinct query mode: proximity, attribute search, detail lookup, and change tracking. No two tools do the same thing, and the descriptions clearly separate find_near from search.
All tools use a consistent verb_noun pattern (find/get/search) with course/courses as the object. Minor variation like 'get_recent_updates' still fits the convention.
Four tools cover a focused read-only disc golf course API without bloat. Each tool addresses a distinct need and the count is well within the ideal 3-15 range.
The surface covers discovery (search and nearby), detail retrieval, and change tracking, which are the core operations for this domain. No obvious missing workflow for a read-only course directory.