Skip to main content
Glama
Open Golf Handicap MCP

Open Golf Handicap MCP

export_golfer_roster

Read-onlyIdempotent

Export your private golfer roster and retained change history to portable JSON for backup, migration, or sharing between systems.

Instructions

Export the private roster and retained change history as portable JSON.

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

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

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint false and a closed world, so the safety profile needs no restating. The description does add genuine context beyond them by disclosing the payload scope (roster plus 'retained' change history) and the serialization format, but it leaves the retention window, payload size, and whether the export is complete or truncated unexplained.

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?

A single sentence with no filler, front-loading the verb and resource before the output format. Every clause contributes information an agent would otherwise lack.

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 no parameters, a present output schema, and rich annotations, the description need only cover scope and format, which it does. It remains thin on selection guidance and on what 'retained' means for the change-history portion, so an agent cannot judge whether this export is exhaustive.

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 per-argument meaning for the description to add and the baseline of 4 applies. The schema is empty and fully closed, so nothing is left ambiguous at the input level.

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 gives a specific verb (Export), a specific resource (the private roster plus retained change history), and an output format (portable JSON), so the agent knows exactly what the call produces. It does not distinguish itself from the related sibling delete_golfer_roster or clarify overlap with roster-reading tools, which keeps it below 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 Guidelines2/5

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

Nothing in the description says when this should be chosen over the other roster-related siblings, nor when it should not be used. The phrase 'portable JSON' hints at backup or migration scenarios but never states that intent, leaving selection entirely to inference.

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