Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_handicap_changes

Read-onlyIdempotent

Retrieve recorded handicap changes for an inclusive UTC interval, up to 5,000 retained observations, to audit or sync handicap data.

Instructions

Read recorded observations for an inclusive UTC interval, up to the retained 5000 changes.

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": {
      "since": "<since>"
    },
    "name": "get_handicap_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYes
untilNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's job is to add context — and it does: timestamps are UTC, the interval is inclusive at both ends, and results are capped at the retained 5000 changes. It does not explain what happens when the cap is exceeded or what the retention window actually is.

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?

A single compact sentence with the behavioral constraints front-loaded and no filler. Slightly dense phrasing ("recorded observations", "retained 5000 changes") costs a little immediate clarity.

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 described, and the retention cap and UTC/inclusive semantics are valuable. Still missing for a two-param temporal query: the required vs optional distinction, the default for an omitted until, and what a "change" record represents.

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 carry parameter meaning; it clarifies that the interval is UTC and inclusive, which is genuinely useful. However it does not state which parameter is required, what happens if until is omitted (presumably open-ended/now), or the accepted timestamp format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb "Read" and resource "recorded observations ... changes" are present, but the description never says these are handicap changes (the tool name and sibling get_handicap_history imply that). An agent must infer the domain and cannot tell from the text alone how this differs from get_handicap_history.

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?

No when-to-use or when-not-to-use guidance is given, and the obvious alternative (get_handicap_history) is not named or contrasted. The agent must guess which retrieval tool applies to its situation.

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