Skip to main content
Glama

PGA withdrawal and injury watch

invoke_pga_injury_watch
Read-onlyIdempotent

PGA Tour withdrawal risk for this week's event: an injury risk score, DraftKings status and alerts, news status, starts in the last 6 and 12 months, withdrawals in the last 6 and 18 months with the last date, days since the last start and events missed. Defaults to golfers in the field, highest risk first. Data refreshes every 30 minutes.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. The plan limit applies on top.
playerNoPlayer name, or part of a name.
in_fieldNoOnly golfers in this week's field. Default true.
min_riskNoLeast injury risk score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: data cadence ('refreshes every 30 minutes') and default sort/filter behavior ('in the field, highest risk first'). It does not mention auth needs or result-size caps, which keeps it below 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.

Conciseness4/5

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

Front-loaded with the core purpose, then the returned fields, then defaults and refresh cadence. The dense field enumeration is justified because there is no output schema, and no sentence is pure filler. Slightly long but well organized.

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 compensates by listing what the tool returns, and it supplies a freshness guarantee and default behavior. Nothing critical is missing for a read-only, single-event query tool, though it could note whether results span only the current event or historical fields.

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% with all four parameters documented inline, so the schema does the heavy lifting. The description adds only that in_field defaults to true and that ordering is by risk descending; it says nothing about limit, player-matching, or min_risk semantics beyond the schema. Baseline 3 is appropriate.

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 resource and scope — 'PGA Tour withdrawal risk for this week's event' — and enumerates the exact data points returned (injury risk score, DK status, withdrawals, days since last start). An agent can distinguish this from pga_projections, pga_optimizer, and pga_schedule without opening any 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?

Gives default behavior ('Defaults to golfers in the field, highest risk first') but never states when to reach for this tool over the other PGA siblings, nor any exclusion conditions. Usage is implied by the returned-data list rather than explicitly guided.

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