Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

update_saved_golfer

Modify a saved golfer's name, nickname, notes, or GHIN number; changing the GHIN clears the existing handicap and change history.

Instructions

Update a saved name, GHIN number, nickname, or notes. Changing GHIN clears the old handicap and its change history.

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": {
      "id": "<id>",
      "patch": "<patch>"
    },
    "name": "update_saved_golfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
patchYes

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The description does real work by disclosing the cascade side effect: changing GHIN wipes the stored handicap and its change history, which is exactly the kind of data-loss warning annotations do not carry. However, that disclosure directly conflicts with the supplied destructiveHint=false, which would tell an agent this mutation is non-destructive. Because the description corrects a misleading annotation rather than merely supplementing it, the conflict itself is a behavioral hazard.

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 mutable fields and followed immediately by the one dangerous consequence. No filler; slightly more economical would be naming the id target explicitly, but nothing here is wasted.

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 annotations plus the GHIN warning cover most of the safety picture. Still missing for a nested-patch mutation tool: what the required 'id' refers to, whether the patch is a partial merge, and any confirmation that the cleared handicap is unrecoverable.

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?

With 0% schema description coverage, the description compensates by enumerating the four nested patch fields (name, GHIN number, nickname, notes), which map cleanly onto the patch object properties. It says nothing about the required 'id' parameter or about patch semantics — whether omitted fields are left unchanged — and the conditional wiping of handicap is stated for GHIN but not tied to any constraint.

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?

States a concrete verb plus the exact updatable fields ('Update a saved name, GHIN number, nickname, or notes'), so the agent knows precisely which resource and which attributes are in scope. It does not distinguish itself from siblings such as save_golfer or save_multiple_golfers, so an agent must infer that this targets an existing saved record by id.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance: no statement that the golfer must already be saved, no pointer to save_golfer for creating one, and no alternative named for related update paths like refresh_saved_handicaps. Usage is only implied by the verb 'Update' against a saved entity.

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