Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_handicap_history

Read-onlyIdempotent

Fetches handicap history for a specified GHIN number in demo mode only; not available for GHIN-login users.

Instructions

Handicap history. Demo mode only: not available with a GHIN login (fails with UNSUPPORTED). Do not offer it to GHIN users.

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": {
      "ghinNumber": "<ghinNumber>"
    },
    "name": "get_handicap_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
ghinNumberYes

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, closed-world operation, so the description adds the non-obvious runtime behavior instead: it will fail with UNSUPPORTED in GHIN mode. That is real value beyond the structured fields. It does not cover pagination or how the limit interacts with results, but with a strong annotation set the bar is met.

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?

Three short sentences, front-loaded with the resource and immediately followed by the constraint that matters most. No filler, though the opening fragment is terse to the point of being under-informative rather than efficient.

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 not be explained, and the safety profile is covered by annotations. What is missing is purpose differentiation from the other handicap tools and any guidance on the two undocumented parameters, which for a 0% coverage schema is a meaningful hole.

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

Parameters2/5

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

Schema description coverage is 0% and there are two parameters, including the required ghinNumber with a digit pattern and a limit defaulting to 20. The description says nothing about either — not the format of ghinNumber, not what limit controls or in what order records come back. With no schema prose to rely on, this is a clear compensation gap.

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

Purpose3/5

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

"Handicap history" names the resource but is close to a restatement of the tool name and gives no verb or scope. With siblings like get_handicap_changes and get_golfer_handicap nearby, the description does nothing to explain what distinguishes this history listing from those tools, leaving the agent to infer it from the name alone.

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?

The exclusion is stated crisply and unambiguously: demo mode only, fails with UNSUPPORTED under a GHIN login, do not offer to GHIN users. That is a genuinely useful pre-condition an agent would otherwise discover only by triggering an error. It stops short of naming the alternative to use for GHIN users, which keeps it out of 5 territory.

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