Skip to main content
Glama

PGA Elo golfer ratings

invoke_pga_elo
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. PGA Elo, calculated by BankrollSZN from every PGA TOUR stroke-play round since 2018, scored as head-to-head strokes against the rest of the same field. rating = 1500 + 50 x skill, where skill is strokes per round better than an average field player. Round head-to-head chance: 1 / (1 + 10^(-(R_A - R_B) / 297)). view top (default): ranked active golfers with rating, skill, rounds, events, change last event, 30 and 90 days, and peak. view movers: biggest risers and fallers last event and over 90 days. view next_event: the next event and the field by rating (fills once round 1 tee times post). view accuracy: backtest 2024 to 2026, round head-to-head log loss 0.67185 vs 0.67455 for a strokes-gained style baseline, accuracy 58.1%. Give player for one golfer. Display only, not a betting signal.

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

Input Schema

NameRequiredDescriptionDefault
viewNoDefault top.
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
playerNoPlayer name, or part of a name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description does add genuinely useful behavior: an approval prompt on first call, and the caveat that next_event only fills once round 1 tee times post, plus 'Display only, not a betting signal.' It does not cover pagination semantics or failure behavior, so it sits above baseline but not at the top.

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 most agent-critical line (approval prompt on first call) is correctly front-loaded, but the rating formula and the 0.67185 vs 0.67455 log-loss digits consume space without helping tool selection or invocation. Dense fragments make it compact but not well-prioritized.

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 describing returns, and it does so per view (fields returned for 'top', what movers/next_event/accuracy contain). A moderately complex four-mode tool is adequately covered, though the row shape and the effect of combining view with player could be stated.

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 coverage is 100%, so 3 is the floor; the description earns more by explaining what each view actually returns, which the enum names alone do not. The player parameter's fuzzy-match behavior is only implied ('part of a name' is in the schema), and limit/offset semantics add nothing 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?

The description names the specific resource (PGA Elo golfer ratings), credits the source (BankrollSZN, stroke-play rounds since 2018) and the method (head-to-head strokes vs. same field). It never explicitly contrasts itself with near-siblings such as invoke_pga_strokes_gained or invoke_pga_projections, so the agent must infer the distinction from content alone.

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?

The four view values are each described with what they contain (top = ranked active golfers; movers = risers/fallers; next_event = next field by rating; accuracy = backtest numbers), and 'Give player for one golfer' tells the agent when to use the player parameter. There is no when-not-to-use guidance and no routing to alternative tools.

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