Skip to main content
Glama

Stymie Golf

by io.github.ThatDudeFreak
OverviewDiscussionsAdmin

Find Nearby Courses

find_nearby_courses
Read-onlyIdempotent

START HERE to plan golf near a place, transit station, address, or US ZIP: pass the place text as location, plus access (public/private/all) and holes (9/18) if known. Coordinates are optional; no slug knowledge is needed. Resolves the location and returns its labeled center and a nearest-first ranked shortlist with canonical Stymie URLs, reusable slugs, straight-line miles, access, holes, and scorecard availability. If the place is ambiguous, ask the golfer to choose a candidate. NEXT call build_golf_trip with the returned latitude/longitude and the same preferences for 1-4 course picks. Use search_courses only for a specific course name. Copy returned URLs verbatim; distances are not drive/transit times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
holesNoTotal course holes; omit if flexible
limitNo
stateNoState/province code, e.g. IL, ON, or NSW, to disambiguate a place
accessNoall
countryNoCountry code to disambiguate a place; GB means UK
latitudeNo
locationNoPlace name, transit station, address, or US ZIP; extract the place from the golfer’s sentence
longitudeNo
distance_milesNoSearch radius in miles: one of 5, 10, 20, 25, 5025

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Country code to disambiguate a place; GB means UK",
+  "enum": [
+    "US",
+    "CA",
+    "GB",
+    "IE",
+    "AU",
+    "NZ"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / holes
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "9",
+        "18",
+        "27",
+        "36"
+      ],
+      "type": "string"
+    },
+    {
+      "const": 9,
+      "type": "number"
+    },
+    {
+      "const": 18,
+      "type": "number"
+    },
+    {
+      "const": 27,
+      "type": "number"
+    },
+    {
+      "const": 36,
+      "type": "number"
+    }
+  ],
+  "description": "Total course holes; omit if flexible"
+}
    • changedInput schema / properties / location / description
      Previous value: -"City, 5-digit ZIP code, or golf destination"New value: +"Place name, transit station, address, or US ZIP; extract the place from the golfer’s sentence"
    • changedInput schema / properties / location / maxLength
      Previous value: -100New value: +200
    • changedInput schema / properties / state / description
      Previous value: -"Optional 2-letter state or province code to disambiguate a city, e.g. ON for Toronto, Canada"New value: +"State/province code, e.g. IL, ON, or NSW, to disambiguate a place"
    • changedInput schema / properties / state / maxLength
      Previous value: -2New value: +3
  2. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Optional 2-letter state code to disambiguate a city"New value: +"Optional 2-letter state or province code to disambiguate a city, e.g. ON for Toronto, Canada"
  3. Changed4 schema fields changed
    • addedInput schema / properties / distance_miles / anyOf
      Added value: +[
+  {
+    "enum": [
+      "5",
+      "10",
+      "20",
+      "25",
+      "50"
+    ],
+    "type": "string"
+  },
+  {
+    "const": 5,
+    "type": "number"
+  },
+  {
+    "const": 10,
+    "type": "number"
+  },
+  {
+    "const": 20,
+    "type": "number"
+  },
+  {
+    "const": 25,
+    "type": "number"
+  },
+  {
+    "const": 50,
+    "type": "number"
+  }
+]
    • addedInput schema / properties / distance_miles / description
      Added value: +"Search radius in miles: one of 5, 10, 20, 25, 50"
    • removedInput schema / properties / distance_miles / enum
      Removed value: -[
-  "5",
-  "10",
-  "20",
-  "25",
-  "50"
-]
    • removedInput schema / properties / distance_miles / type
      Removed value: -"string"
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it reveals behavior: location resolution returns a labeled center, results are nearest-first, URLs must be copied verbatim, and distances are straight-line miles not drive/transit times. It also notes coordinates and slug knowledge are optional and warns about ambiguous locations. No contradiction with annotations.

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

Conciseness5/5

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

The main guidance is front-loaded ('START HERE'), and every sentence adds distinct value: input requirements, return contents, ambiguity handling, next step, and a caveat about distance types. No filler.

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

Completeness5/5

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

For a 9-parameter tool with no output schema, the description covers input, output shape, ranking, URL handling, error/ambiguity behavior, and links to related workflow tools. Nothing essential for invoking it correctly is missing.

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?

With 56% schema description coverage, the description compensates for the most important parameters: location can be place/station/address/ZIP, access/holes are the key filters to pass when known, and coordinates are optional. It omits limit and distance_miles semantics, though those are documented in the schema, so the gap is minor.

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 'START HERE to plan golf near...' and states a specific verb/resource: resolve a location and return a ranked shortlist of nearby courses. It clearly differentiates itself from search_courses ('only for a specific course name') and build_golf_trip (the next step).

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?

Provides explicit when-to-use guidance: use this tool first for location-based course planning, use search_courses only for a specific course name, and follow with build_golf_trip. It also handles ambiguity by instructing the agent to ask the golfer to choose a candidate.

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