Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

save_golfer

Add one explicitly requested golfer to your private roster using name and GHIN number. Use for individual entries; use save_multiple_golfers for screenshot imports.

Instructions

Add one explicitly requested golfer to the private roster. Use save_multiple_golfers for screenshot imports.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
notesNo
nicknameNo
ghinNumberYes

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent write, and the description correctly reinforces the write framing plus adds the 'private roster' scope and the 'explicitly requested' safeguard. It does not say what happens when the ghinNumber already exists (error vs. overwrite), which matters given idempotentHint=false.

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?

Two short sentences with no filler; the single-record scope is front-loaded and the sibling routing follows immediately.

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 write semantics are partly covered by annotations. However, with zero parameter documentation and no duplicate/conflict behavior stated for a non-idempotent create, an agent lacks what it needs to call this safely on repeat inputs.

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 4 parameters, so the description carries the burden but adds nothing: it never mentions name, ghinNumber (format/length expectations), nickname, or notes, nor which are required. An agent must read the raw schema patterns to understand the inputs.

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 ('Add one ... golfer'), names the destination ('private roster'), and explicitly limits scope to a single record, which distinguishes it from the sibling save_multiple_golfers in the same sentence pair.

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 a clear selection rule: single explicitly-requested golfers go here, screenshot imports go to save_multiple_golfers; 'explicitly requested' also implicitly warns against adding golfers the user did not ask for. No guidance on how this relates to updating an already-saved golfer, but the primary alternative is named with its condition.

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