Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_saved_golfers

Read-onlyIdempotent

Retrieve your saved golfer roster and optionally filter it by name or nickname to find a specific golfer quickly.

Instructions

Retrieve the authenticated user’s private roster, optionally search names or nicknames.

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed operation. The description adds useful context that the roster is private and tied to the authenticated user, but it does not discuss pagination, result limits, or other behavioral details.

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?

The definition is a single front-loaded sentence with no redundant wording. It communicates the core action and optional filter efficiently.

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?

For a simple one-parameter read tool with an output schema, the description covers the essential context: authenticated scope, private roster, and optional search. Minor details such as pagination or empty-query behavior are left to the schema or output contract.

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 description coverage is 0%, so the description must explain the single optional parameter. It does so by stating that the query searches names or nicknames, which gives the parameter clear meaning beyond the bare string schema.

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 uses a specific verb and resource: retrieve the authenticated user’s private roster. It also clarifies the optional search behavior, though it does not explicitly distinguish this from sibling tools such as search_golfers.

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?

Usage is implied: fetch the saved roster, optionally filtering by name or nickname. There is no explicit when-to-use guidance, no exclusions, and no named alternative for broader golfer searches.

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