Skip to main content
Glama

SportStatsAPI

Get golf leaderboard

get_golf_leaderboard
Read-only

A golf tournament's leaderboard: position (tied), to par, strokes per round, thru and today while live, earnings, missed cut or withdrawn, and per-player stats (birdies, eagles, driving distance and accuracy, greens in regulation, putts); holes=true adds hole-by-hole scores.

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": {
      "tournament_id": "<tournament_id>"
    },
    "name": "get_golf_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
holesNoalso each player's hole-by-hole scores (large)
tournament_idYestournament code (or number) from get_golf_tournaments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tournament_id / description
      Previous value: -"tournament id from get_golf_tournaments"New value: +"tournament code (or number) from get_golf_tournaments"
    • changedInput schema / properties / tournament_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

The description reveals that some values (thru, today) are live/volatile, which is consistent with idempotentHint=false and useful context beyond the annotations. It also warns that holes=true produces a large payload. However it does not state what happens for non-live or completed events, nor any rate/permission considerations, so the addition is modest against an already read-only annotated tool.

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 dense sentence front-loads the resource and then lists returnable fields efficiently, with the holes flag called out at the end. It is compact, though the long semicolon-separated field list takes effort to parse.

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 no output schema, the description carries the burden of explaining return values and does so thoroughly, covering positions, scoring, statuses, and stat categories. Minor gaps remain around behavior for finished events and whether absent fields are omitted versus null.

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 100%, so both parameters are already documented, establishing a baseline of 3. The description reinforces holes=true as adding hole-by-hole scores and flags the size cost, but adds no format or validity details beyond the 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?

Names a specific resource (a golf tournament's leaderboard) and enumerates exactly what it returns, including live-only fields (thru, today) and status states (missed cut, withdrawn). It is clearly distinguishable from get_golf_tournaments and get_golf_player, though it is phrased as a noun list without an explicit verb.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only routing cue is the schema note that tournament_id comes from get_golf_tournaments, which is schema text rather than description guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources