Stymie Golf

Build Golf Trip

build_golf_trip

Read-onlyIdempotent

AFTER find_nearby_courses, pass its center latitude/longitude, access and holes preferences, and number_of_courses to make a 1-4 course shortlist. You can also start directly with a plain-language location (place, station, address, or US ZIP). Optional tee yardage and slope ranges rank matching tees by fit plus straight-line distance; without tee preferences, courses are nearest-first and missing scorecards are retained. Returns ranked course picks with canonical Stymie URLs, reusable slugs, selection reasons, distance, access, holes, and published tee data when available. Public access excludes unknown/private courses; private picks require the golfer to confirm access. No booking, tee-time availability, transit routing, or drive times are provided. Use returned URLs as citations without inventing slugs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`holes`	No
`state`	No
`access`	No		public
`country`	No	Country code to disambiguate a place; GB means UK
`latitude`	No
`location`	No	Place name, station, address, or US ZIP; omit when reusing the nearby result coordinates
`longitude`	No
`slope_max`	No
`slope_min`	No
`tee_yards_max`	No
`tee_yards_min`	No
`distance_miles`	No	Search radius in miles: one of 5, 10, 20, 25, 50	25
`number_of_courses`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 22, 2026

addedInput schema / properties / access

Added value: +{
+  "default": "public",
+  "enum": [
+    "all",
+    "public",
+    "private",
+    "semi_private",
+    "municipal",
+    "resort"
+  ],
+  "type": "string"
+}

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"
+}

changedInput schema / properties / distance_miles / anyOf

Previous value: -[
-  {
-    "enum": [
-      "10",
-      "20",
-      "25",
-      "50"
-    ],
-    "type": "string"
-  },
-  {
-    "const": 10,
-    "type": "number"
-  },
-  {
-    "const": 20,
-    "type": "number"
-  },
-  {
-    "const": 25,
-    "type": "number"
-  },
-  {
-    "const": 50,
-    "type": "number"
-  }
-]New 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"
+  }
+]

changedInput schema / properties / distance_miles / description

Previous value: -"Search radius in miles: one of 10, 20, 25, 50"New value: +"Search radius in miles: one of 5, 10, 20, 25, 50"

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"
+    }
+  ]
+}

addedInput schema / properties / location / description

Added value: +"Place name, station, address, or US ZIP; omit when reusing the nearby result coordinates"

changedInput schema / properties / location / maxLength
```
Previous value: -100New value: +200
```
removedInput schema / properties / slope_max / default
```
Removed value: -155
```
removedInput schema / properties / slope_min / default
```
Removed value: -115
```
changedInput schema / properties / state / maxLength
```
Previous value: -2New value: +3
```
removedInput schema / properties / tee_yards_max / default
```
Removed value: -6200
```
changedInput schema / properties / tee_yards_max / minimum
```
Previous value: -4000New value: +500
```
removedInput schema / properties / tee_yards_min / default
```
Removed value: -5900
```
changedInput schema / properties / tee_yards_min / minimum
```
Previous value: -4000New value: +500
```

Changed4 schema fields changedSep 19, 2026

addedInput schema / properties / distance_miles / anyOf

Added value: +[
+  {
+    "enum": [
+      "10",
+      "20",
+      "25",
+      "50"
+    ],
+    "type": "string"
+  },
+  {
+    "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 10, 20, 25, 50"

removedInput schema / properties / distance_miles / enum

Removed value: -[
-  "10",
-  "20",
-  "25",
-  "50"
-]

removedInput schema / properties / distance_miles / type
```
Removed value: -"string"
```

First observedAug 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly, idempotent, and openWorld annotations, the description reveals ranking behavior, nearest-first fallback, retention of missing scorecards, public-access filtering, private-course confirmation requirements, and the instruction to use returned canonical URLs as citations. This is substantive context that materially affects how the agent invokes and uses the tool.

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 long but information-dense, with the primary workflow front-loaded in the first sentence. Every clause adds useful operational detail, and the length is justified by the complexity of a 13-parameter tool, though a few caveats could be grouped more tightly.

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 a complex tool with no output schema, the description covers invocation modes, ranking logic, return contents, access handling, exclusions, and citation guidance, making it nearly complete. It omits a couple of parameter clarifications like state and distance_miles, but an agent can still call it correctly and interpret results based on this text.

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 description coverage is only 23%, and the description compensates well by explaining latitude/longitude, location, access, holes, number_of_courses, and tee yardage/slope ranges. It does not explicitly cover state, distance_miles, or country, so some parameters still rely on schema or inference.

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 clearly names the operation as building a golf trip shortlist, specifies the output as a 1-4 course ranked selection, and ties itself to find_nearby_courses while also supporting direct location input. This distinguishes it from the search-related siblings without requiring the agent to open their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit workflow guidance: use after find_nearby_courses and pass its coordinates/preferences, or start directly with a plain-language location. It also states exclusions such as no booking, tee-time availability, transit routing, or drive times, but it does not explicitly name alternative sibling tools for those broader search or booking scenarios.

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

All Stymie Golf tools Inspect

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

Need Help?