Skip to main content
Glama

NS Pros MCP Gateway

golfcore__search

Search everything GolfCore holds for more than 30,000 golf courses in more than 180 countries and territories. Ask by course name ('Pebble Beach'), by its name in local script ('宮崎カントリークラブ'), by architect ('Donald Ross'), by slug ('pebble-beach'), by place, passing just the place name ('St Andrews', 'Monterey'), or about GolfCore itself ('what does a caddie master use GolfCore for'). A course comes back with its address, town, region, country, coordinates, timezone, phone and website, its archit

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "golfcore__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoOptional. A point to search around, such as the person's location or their hotel. Courses come back nearest first, each with its distance in miles.
limitNoResults per scope. Default 5, maximum 20.
queryNoWhat you are looking for, in plain English. May be empty when near is given; with near, it filters courses by name or town.
scopeNoOptional. Narrow the search to these scopes: 'slug' treats the query as a GolfCore course slug and returns that exact course, 'courses' matches courses by name and town, 'scorecards' attaches each course's per-hole card and tee ratings to it, 'city', 'region' and 'country' return pages that count and list every course in a place, 'product' returns GolfCore's own pages. Omit to search all of them. Combine freely, e.g. ["slug","scorecards"] for one exact card, or ["city","courses"]. Leave 'scorecards' out when you only need to know which courses exist; the cards are large.
coverageNoOptional. Only courses GolfCore has this for: 'contours' lidar green contour maps, 'traced' a traced course map, 'scorecard' a hole-by-hole card, 'rated' USGA course and slope ratings.
radius_milesNoOptional, with near. How far to look, in miles. Default 25, maximum 250.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does meaningful work: it states that results are courses with address, town, region, country, coordinates, timezone, phone, and website, and that near searches return nearest-first with distance in miles. It also warns that scorecards are large, which is useful behavioral context. It does not cover authentication, rate limits, or failure behavior, but for a read-only search that is a minor gap.

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 definition is front-loaded with the purpose and then supplies useful examples rather than filler. It is longer than necessary, and the truncated ending suggests some sprawl, but every sentence is largely functional.

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 six-parameter search tool with no output schema and no annotations, the description covers query interpretation and return contents well. It does not explain every scope exhaustively, but the schema handles those details, so an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains near, limit, query, scope, coverage, and radius_miles in detail. The description adds illustrative query forms, but it does not add much semantic meaning beyond the schema, which is the baseline expectation when the schema is fully documented.

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 everything GolfCore holds across 30,000+ courses in 180+ countries. It immediately makes clear this is a broad lookup tool, distinct from account or billing siblings, and the query examples sharpen what kind of search it performs.

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 extensive when-to-use guidance through concrete query patterns: course name, local script, architect, slug, place name, and even questions about GolfCore itself. It does not explicitly name alternatives such as ask_caddie or explain when not to use this tool, but the usage context is otherwise clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.