Skip to main content
Glama

NS Pros MCP Gateway

golfcore__distance_to_flag

How far the golfer is from the flag, from where they are standing: 'how far is that flag', 'what's the yardage'. Returns the course, the hole, its par and stroke index, and yards to the flag (today's pin as the club set it) and to the middle of the green. Pass lat and lng only if your device gives you the golfer's GPS position; otherwise call it with no arguments, and GolfCore reads the golfer's position from the GolfCore app on their phone. It is part of GolfCore Premium: the golfer signs in to

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

Input Schema

NameRequiredDescriptionDefault
latNoOptional. The golfer's precise latitude, only when your device gives you their GPS position. Never ask the golfer for coordinates: leave lat and lng out and GolfCore uses the position from the GolfCore app on their phone.
lngNoOptional. The golfer's precise longitude, with lat.
holeNoOptional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position.
courseNoOptional. The course slug, when known. Otherwise the course is found from the position.
accuracy_mNoOptional. The location's horizontal accuracy in meters, when the device reports it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose a lot: it enumerates the return payload (course, hole, par, stroke index, yards to today's pin and to the middle of the green) and notes a Premium/sign-in requirement. However, that final Premium sentence is cut off mid-clause ('the golfer signs in to'), so the auth/eligibility condition is not actually actionable, and nothing is said about failure modes when no position or course is available.

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

Conciseness3/5

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

The core content is front-loaded and useful, but the trailing Premium sentence is truncated mid-word and conveys no completable information, and the lat/lng instruction duplicates schema text. Removing or completing that tail would tighten the definition considerably.

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?

There is no output schema, so the description rightly explains the return shape, and with no annotations it also covers invocation and position sourcing. The only real hole is the incomplete Premium/auth sentence, which leaves a gating condition unresolved for a tool that may fail for non-subscribers.

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% and the schema already explains each optional parameter, including the 'never ask the golfer for coordinates' rule. The description largely restates the lat/lng guidance rather than adding new meaning, and it says nothing about how hole/course overrides interact with a supplied position. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific measurement ('How far the golfer is from the flag, from where they are standing') and backs it with user phrasings ('how far is that flag', 'what's the yardage'), so the agent can map a natural request to this tool unambiguously. It does not explicitly contrast with nearby tools like ask_caddie or search, but the resource is narrow enough that confusion is unlikely.

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 an explicit conditional rule: pass lat/lng only if the device supplies GPS, otherwise call with no arguments and GolfCore reads position from the app. That resolves the main invocation ambiguity for a zero-required-param tool. It stops short of saying when to prefer this over ask_caddie or what to do when the golfer isn't on a mapped course.

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.