Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

disconnect_provider

Destructive

Disconnect the owner's provider session, clear cached lookup data, and report whether stored provider credentials remain so you can verify sign-out status.

Instructions

Disconnect this owner's provider session, purge lookup cache, and report whether provider credentials remain stored. Remote revocation depends on the provider. Revoke MCP grants separately at their issuer.

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

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 flag destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds substantive context beyond that by disclosing the cache purge, that credentials may remain stored after the call, and that remote revocation is not guaranteed. The remaining gap is that repeat-call behavior and the local-vs-remote distinction are only implied.

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?

Three short sentences, front-loaded with the primary action and effects, then caveats, then scope boundaries — no filler. The phrase 'at their issuer' is slightly compressed and could be clearer, but nothing is wasted.

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?

With an output schema present, the description needn't explain the return payload, and the parameterless schema needs no documentation, so the burden is purely behavioral — which it largely meets. It could be stronger by stating whether local credentials are actually removed or merely reported on.

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 parameters, so there is no parameter semantics to add and the baseline applies. The description correctly implies the operation is scoped to 'this owner' rather than accepting an owner argument.

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 and resource ('Disconnect this owner's provider session') and enumerates the accompanying effects (cache purge, credential-status report). It clearly is not a grant-revocation tool, but it never names the sibling status-check tool (get_connection_status) or explains how it differs from simply inspecting connection state.

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?

Provides an explicit exclusion — MCP grants must be revoked separately at their issuer — which steers the agent away from expecting this call to fully de-authorize. It also warns that remote revocation is provider-dependent, but gives no positive trigger conditions (e.g., when to prefer this over checking status first).

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