Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_course_handicap

Read-onlyIdempotent

Calculate a golf Course Handicap from a Handicap Index and supplied 9- or 18-hole course rating, slope, and par; use negative indexes for plus handicaps. Playing Handicap allowance is not applied.

Instructions

Educational local Course Handicap calculation for supplied 9- or 18-hole ratings. Use negative numbers for plus indexes. Does not apply a Playing Handicap allowance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handicapIndex": "<handicapIndex>",
      "holes": "<holes>",
      "slope": "<slope>",
      "courseRating": "<courseRating>",
      "par": "<par>"
    },
    "name": "get_course_handicap"
  }
}

Input Schema

NameRequiredDescriptionDefault
parYes
holesYes
slopeYes
courseRatingYes
handicapIndexYes

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuine scope information: it is educational/local rather than an official handicap, and no Playing Handicap allowance is applied. It says nothing about rounding or precision of the returned figure, which matters for a calculation 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?

Two short sentences, front-loaded with the purpose, with no filler. The negative-index instruction and the Playing Handicap exclusion are both load-bearing, though the dense "Educational local" phrasing is slightly opaque on first read.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and range constraints live in the schema. Even so, for a five-required-parameter calculation tool with no per-parameter schema descriptions, the omission of units/meaning for courseRating, slope and par leaves the agent under-equipped to supply correct inputs.

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 0% across five required parameters, so the description must compensate. It usefully clarifies the sign convention for plus indexes (handicapIndex) and that the rating inputs are for 9 or 18 holes, but slope, courseRating and par are left completely unexplained in both schema and description.

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 description states a specific operation on a specific resource: a local Course Handicap calculation from supplied ratings. "Educational local" distinguishes it from an official/authoritative handicap retrieval such as get_golfer_handicap, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

It provides one real scope exclusion ("Does not apply a Playing Handicap allowance"), which tells the agent this tool is not for Playing Handicap math, plus an input convention. There is no explicit when-to-use framing or pointer to which sibling handles official or Playing Handicap values, so routing is only implied.

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