Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

delete_golfer_roster

Destructive

Preview, then confirm and clear all golfer roster and history data plus cache. Backups must be removed separately by their owner.

Instructions

Preview deletion first. After explicit user confirmation, submit the returned token and confirmed=true. Clears all roster and history content plus cache; an encrypted empty revision record remains. Backups must be removed separately by their owner.

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

Input Schema

NameRequiredDescriptionDefault
confirmedNo
confirmationTokenNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds genuinely new behavior: exactly what is destroyed (roster, history, cache), what survives (an encrypted empty revision record), and that backups must be removed separately by their owner. That is the kind of consequence detail an agent needs before a destructive call.

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?

Four short sentences, front-loaded with the mandatory preview-then-confirm workflow, followed by destruction scope and the backup caveat. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive two-parameter tool with an output schema supplying the preview token, the description covers workflow, irreversible effects, retained artifacts, and an out-of-band caveat. Nothing essential to correct invocation is missing.

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 coverage is 0%, so the description must carry the parameters, and it does: confirmed=true and the confirmation token returned by the preview, including the ordering dependency. It does not describe token format or expiry, which is a minor residual gap.

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 specific verb+resource and precise scope: it clears all roster and history content plus cache, leaving an encrypted empty revision record. That distinguishes it in spirit from per-golfer tools like remove_saved_golfer, though no sibling is named explicitly.

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 an explicit procedural requirement: preview first, then call with the returned token and confirmed=true only after explicit user confirmation. It does not state when to prefer this over alternatives such as remove_saved_golfer, so it stops short of full routing guidance.

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