Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_recent_scores

Read-onlyIdempotent

Retrieve recent golf scores in demo mode for a GHIN number; GHIN logins are unsupported.

Instructions

Recent scores. 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_recent_scores"
  }
}

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.3/5.0
Behavior3/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds the genuinely useful failure mode (UNSUPPORTED under a GHIN login). It says nothing beyond that about ordering, freshness window, or what 'recent' means, and nothing about the required ghinNumber lookup.

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

Conciseness5/5

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

Three very short sentences with zero filler; the availability restriction is front-loaded immediately after the purpose statement, which is exactly where an agent needs it.

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 described, and the annotations cover safety. But for a tool with a required identifier parameter at 0% schema coverage, the description should at least say that a GHIN number is the lookup key and that limit caps the result count.

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% across two parameters, so the schema supplies only names, types and a pattern. The description never mentions ghinNumber or limit, leaving the default of 20 and the 1-100 range entirely to the schema with no interpretive help.

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?

The description is a bare noun phrase, 'Recent scores', without a verb or any detail on what a 'score' record contains or how 'recent' is bounded. It does differentiate itself from handicap-oriented siblings by dealing in scores, but an agent gets only a category, not a clear operation.

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 environment gate: demo mode only, unavailable with a GHIN login, and a direct instruction not to offer it to GHIN users. That is unusually strong when-not guidance; the only gap is that no alternative tool is named for the GHIN-user case.

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