Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_golfer_handicap

Read-onlyIdempotent

Retrieve a Handicap Index by GHIN number, or omit it to get the signed-in user's own handicap. Returns source and synthetic provenance; unknown or unavailable golfers return errors.

Instructions

Retrieve one Handicap Index by GHIN number, with source and synthetic provenance. Omit ghinNumber to look up the signed-in user's own handicap (for "what's my handicap"). Unknown or unavailable golfers return errors. Force still obeys request limits.

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": "get_golfer_handicap"
  }
}

Input Schema

NameRequiredDescriptionDefault
ghinNumberNo
forceRefreshNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value with error behavior for unknown/unavailable golfers and the note that forced requests still respect request limits. It is a bit terse ('Force still obeys request limits' never names the parameter) but does disclose rate-limit behavior beyond annotations.

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?

Four short sentences, front-loaded with the core action and then the self-lookup case, error behavior, and rate-limit caveat. There is no filler, though the phrase 'Force still obeys request limits' is abrupt and would be clearer if it named forceRefresh.

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?

With an output schema present, the description needn't document return values, and it notes provenance is returned. For a two-optional-parameter read tool this covers the important cases (self lookup, unknown golfers, rate limits); only minor details like the GHIN number format are left entirely to the schema.

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 0%, so the description must carry parameter meaning, and it does: ghinNumber is the GHIN lookup key and omitting it means the caller's own handicap, while 'force' implies a refresh that is rate-limited. The 6-10 digit pattern and forceRefresh default false are left to the schema, but the semantic intent of both parameters is explained.

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?

States a specific verb and resource ('Retrieve one Handicap Index by GHIN number') and explicitly scopes to a single record, which distinguishes it from the plural sibling get_multiple_handicaps. It also names the alternate mode of the same tool (omitting the number for the signed-in user).

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?

Gives clear when-to-use guidance: 'Omit ghinNumber to look up the signed-in user's own handicap (for "what's my handicap")' tells the agent exactly which case this tool serves. It does not explicitly exclude or route to named siblings such as get_multiple_handicaps or get_handicap_history, so it stops short of full alternative coverage.

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