Skip to main content
Glama

Stymie Golf

by io.github.ThatDudeFreak
OverviewDiscussionsAdmin

Search Courses

search_courses
Read-onlyIdempotent

Search for a named course or filter the directory by city/state, access, and holes. For a trip near a place, station, address, or ZIP, call find_nearby_courses FIRST; do not put the place name in query (query searches course names). You may also pass location here for a proximity search. Returns canonical Stymie URLs, reusable slugs, access, holes, scorecard availability, and straight-line miles when a location is supplied. Copy returned URLs; never construct county slugs. Next: get_course with a returned URL, or build_golf_trip with the resolved center and preferences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoUS ZIP; use location for other places
cityNoCity name
pageNoPage number
typeNoCourse type filter
holesNoNumber of holes
limitNoResults per page (max 50)
queryNoCourse name search (partial match)
stateNoState/province code, e.g. IL, ON, NSW
countryNo
locationNoPlain-language place, station, address, or US ZIP; find_nearby_courses is the recommended first step for trips
distance_milesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "enum": [
+    "US",
+    "CA",
+    "GB",
+    "IE",
+    "AU",
+    "NZ"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / distance_miles
      Added value: +{
+  "default": 50,
+  "maximum": 50,
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / holes / anyOf
      Added value: +[
+  {
+    "enum": [
+      "9",
+      "18",
+      "27",
+      "36"
+    ],
+    "type": "string"
+  },
+  {
+    "const": 9,
+    "type": "number"
+  },
+  {
+    "const": 18,
+    "type": "number"
+  },
+  {
+    "const": 27,
+    "type": "number"
+  },
+  {
+    "const": 36,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / holes / enum
      Removed value: -[
-  "9",
-  "18",
-  "27",
-  "36"
-]
    • removedInput schema / properties / holes / type
      Removed value: -"string"
    • addedInput schema / properties / location
      Added value: +{
+  "description": "Plain-language place, station, address, or US ZIP; find_nearby_courses is the recommended first step for trips",
+  "maxLength": 200,
+  "type": "string"
+}
    • changedInput schema / properties / state / description
      Previous value: -"2-letter state code, e.g. \"NJ\""New value: +"State/province code, e.g. IL, ON, NSW"
    • changedInput schema / properties / state / maxLength
      Previous value: -2New value: +3
    • changedInput schema / properties / zip / description
      Previous value: -"5-digit ZIP code for proximity search (50 mile radius)"New value: +"US ZIP; use location for other places"
    • removedInput schema / properties / zip / maxLength
      Removed value: -5
    • removedInput schema / properties / zip / minLength
      Removed value: -5
    • addedInput schema / properties / zip / pattern
      Added value: +"^\\d{5}$"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context: it lists what is returned (canonical URLs, slugs, access, holes, scorecard availability, miles) and warns 'never construct county slugs.' This goes beyond annotations and gives the agent actionable behavioral guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph but well-structured: it fronts the core purpose, then provides usage routing, then the return contract, and finishes with next-step guidance. Every sentence serves a purpose; there is no filler. It is slightly longer than strictly necessary but earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no output schema and many siblings, the description is thorough. It explains the primary use case, how it differs from find_nearby_courses, what the output contains, and how to chain to other tools. It does not explain every filter parameter (type, holes, country), but those are self-evident and covered by the schema. The description is sufficient for correct invocation.

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?

Schema coverage is 82%, so most parameters are already documented. The description adds critical meaning: it clarifies that 'query' searches course names only, not places, and that 'location' may be used for proximity search. This resolves potential ambiguity between query and location, which the schema alone does not fully capture.

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 opens with a specific verb and resource: 'Search for a named course or filter the directory by city/state, access, and holes.' It immediately distinguishes itself from find_nearby_courses by stating that tool should be called first for trips. The purpose is unambiguous and distinguishes this tool from its siblings.

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?

Explicitly states when to use find_nearby_courses instead ('For a trip near a place, station, address, or ZIP, call find_nearby_courses FIRST'), and warns against putting place names in query because 'query searches course names.' It also provides clear follow-up actions (get_course or build_golf_trip), leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Stymie Golf toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources