Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

pgatour_tournament_broadcast

Retrieve PGA tournament regional broadcast schedules, network metadata, and source country codes by year, slug, and main-tour ID; no media streams are fetched.

Instructions

Get PGA tournament broadcast coverage. Returns native regional broadcast schedules, network metadata and the actual source country code. There is no country selector or worldwide-coverage promise. Direct media stream URLs are omitted; no stream is fetched. Use year, slug and full main-tour ID from tournament-link discovery.

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": {
      "year": "<year>",
      "slug": "<slug>",
      "id": "<id>"
    },
    "name": "pgatour_tournament_broadcast"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Complete main-tour tournament ID
`slug`	Yes	Native tournament URL slug from link discovery
`year`	Yes	Four-digit native tournament URL year

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it states the return contents, that streams are not fetched and stream URLs are omitted, and that coverage is region-native rather than global. These are genuine behavioral traits an agent cannot get from the schema. It does not mention auth, rate limits, or what an empty/unsupported-region response looks like.

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?

Four short sentences, front-loaded with the purpose before the negative constraints and the parameter provenance. Mild redundancy in 'Direct media stream URLs are omitted; no stream is fetched', where one clause would carry the same meaning, but nothing is padded.

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?

No output schema exists, so the description rightly spends its opening on what is returned (schedules, network metadata, country code) and confirms what is not (stream URLs). Combined with full schema coverage on three required parameters, an agent has enough to call it correctly; the only missing piece is guidance on sparse or unsupported regions.

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 coverage is 100%, so the schema already documents 'year', 'slug' and 'id' including that the ID must be the complete main-tour ID. The description reinforces the provenance ('from tournament-link discovery') but adds no format, constraint or validation detail 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?

Names a specific verb and resource ('Get PGA tournament broadcast coverage') and immediately scopes the payload to native regional broadcast schedules, network metadata and source country code. That scope distinguishes it cleanly from sibling tournament tools such as weather, tee times and course stats without needing to name them.

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?

Explicitly excludes a commonly assumed use case ('no country selector or worldwide-coverage promise'), which tells the agent when this tool will not answer a worldwide-broadcast question. It also points at the prerequisite source for all three parameters ('from tournament-link discovery'), effectively routing the agent to pgatour_tournament_links first. It stops short of naming a concrete alternative for cross-country coverage.

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

Deploy Server