Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

refresh_saved_handicaps

Refresh all or selected saved golfers' handicap indexes, preserve cached retrieval times, keep last valid handicaps on failure, and report each change individually.

Instructions

Refresh all or selected saved golfers. Cached reads keep their original retrieval time. Preserve last valid handicaps on failure and report changes individually.

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

Input Schema

NameRequiredDescriptionDefault
idsNo
forceRefreshNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description adds genuinely useful behavior: cached reads retain their original retrieval time, failures preserve the last valid handicaps, and changes are reported per item. This explains the partial-failure and caching semantics an agent would otherwise have to guess. It does not cover auth or provider-call implications, keeping it at 4 rather than 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, information-dense sentences with the scope stated first and behavioral caveats following. Phrasing is terse to the point of ambiguity in places ("saved golfers" vs. handicaps, and the cache sentence reads opaquely without forceRefresh context), but nothing is padding.

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?

With an output schema present, the description rightly focuses on behavior rather than return shape, and it covers failure handling and reporting granularity well. However, for a non-read-only refresh tool with a forceRefresh switch, the omission of what forceRefresh does is a material completeness gap.

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%, so the description must carry parameter meaning. It indirectly conveys the ids list via "all or selected," but forceRefresh — the most consequential toggle — is never explained (does it bypass the cache, and how does it interact with the stated cache-retention behavior?). That gap leaves a key parameter's semantics undefined in both schema and prose.

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?

A specific verb (refresh) and scope (all or selected saved golfers) are stated up front, and the handicap-update intent becomes clear from the following sentences. There is a mild resource mismatch between the name (refresh_saved_handicaps) and the first sentence (refresh saved golfers), and no sibling is named for contrast, 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 Guidelines3/5

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

"All or selected" implies the two usage modes and the ids parameter supplies the selection path, but there is no explicit when-to-use versus get_multiple_handicaps/get_handicap_history, and no when-not guidance. Usage is inferable rather than stated.

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