Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

save_multiple_golfers

Preview and confirm multiple golfer records before saving them to an encrypted roster, showing duplicates and requiring a short-lived token for final submission.

Instructions

Preview image-derived or text records first with confirmed=false. Show the returned records and duplicates to the user. Only after explicit confirmation resend identical records, confirmed=true, and the returned token (valid 5 minutes). No images are stored.

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": {
      "golfers": "<golfers>"
    },
    "name": "save_multiple_golfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
golfersYes
confirmedNo
confirmationTokenNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description carries real weight and delivers: a two-phase confirmation requirement, a 5-minute token lifetime, and the assurance that no images are stored. It does not say what happens to records that fail validation or how duplicates are resolved, which keeps it from a 5.

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 preview step and ending with the no-image-storage guarantee. Every sentence carries information; the only mild inefficiency is that the workflow is described in imperative prose rather than a compact sequence.

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, return values need no explanation, and the description covers the workflow, token expiry, and storage behavior. The remaining gap is the shape and limits of the golfers payload, which is left entirely to the schema.

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?

Schema description coverage is 0%, so the description must compensate. It explains the semantics of confirmed (preview vs. commit) and confirmationToken (returned token, valid 5 minutes), which is genuinely useful, but it says nothing about the golfers array's fields (name, ghinNumber, notes, nickname) or the 100-item cap.

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?

The description conveys a batch-save of golfer records with a mandatory preview-then-confirm flow, naming the key mechanics (confirmed flag, token). It never states plainly that records are persisted to the saved-golfer roster, and it does not distinguish itself from the single-record save_golfer sibling, so it stops short of a 5.

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 explicit sequencing: call with confirmed=false first, show returned records and duplicates to the user, and only resend with confirmed=true after explicit confirmation. That is clear when-to-use guidance, but it offers no exclusion or comparison against save_golfer or update_saved_golfer.

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