Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

get_connection_status

Read-onlyIdempotent

Check GHIN authentication, credential-storage status, expiry, and available capabilities before looking up handicaps—without exposing credentials.

Instructions

Inspect MCP identity, provider authentication, credential-storage status, expiry, capabilities and limitations; never returns credentials. yourGhinNumber is the user's own GHIN number if they saved one at login: use it for questions like "what's my handicap"; if it is null, ask the user for their number.

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_connection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them: it explicitly promises credentials are never returned and enumerates the diagnostic surface (auth state, credential storage, expiry, capabilities/limitations). It stops short of describing failure modes or what happens when no provider is connected, 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is dense but efficient and front-loads the security guarantee. The second sentence is confusingly assembled: its pronoun 'use it' is ambiguous between the tool and the returned yourGhinNumber value, and the colon structure forces the reader to parse output-field guidance inside a no-parameter description.

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?

An output schema exists, so the return-value enumeration is partly redundant, but the 'never returns credentials' guarantee and the null-handling instruction are exactly the kind of context a schema cannot convey. For a zero-parameter diagnostic tool this is close to complete; only the no-provider/error path is unaddressed.

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?

The tool takes zero input parameters, so there is nothing for the description to disambiguate; baseline is 4. The yourGhinNumber discussion actually describes an output field rather than an input, so it adds no parameter meaning here, but it does not misrepresent the schema either.

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

Purpose5/5

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

States a specific verb ('Inspect') plus the exact resources surfaced: MCP identity, provider authentication, credential-storage status, expiry, capabilities and limitations. That scope is clearly distinct from every sibling (handicap, score, and roster tools), so an agent can select it without opening the schema.

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?

Provides situational guidance only for the secondary yourGhinNumber flow ('use it for questions like "what's my handicap"; if it is null, ask the user for their number'), which is useful routing advice. It never states when to call this tool itself versus e.g. get_golfer_handicap, nor any preconditions such as requiring a provider connection, so the when-to-use is implied rather than stated.

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