Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pgatour_tournament_links

Retrieve PGA tournament URL contexts—year, slug, and ID—from actual schedule and sitemap links, while listing unmatched schedule events separately without guessing slugs.

Instructions

Discover PGA tournament URL contexts. Returns year, slug and ID from actual main-tour schedule/sitemap links. Schedule events without a matching source link are listed separately; their slugs are not guessed. Use returned contexts with tournament tab endpoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses one real behavioral trait — slugs are never fabricated and unmatched schedule events are surfaced separately — but says nothing about whether this makes HTTP calls, caching, rate limits, or the shape of the 'listed separately' entries despite there being no output schema.

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 what is returned before the edge-case caveat and the usage directive. Slightly jargon-heavy ('URL contexts') and a bit terse, but nothing is redundant.

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?

For a zero-parameter, no-output-schema discovery tool, the description covers the return fields and the important edge case, which is most of what an agent needs to call it. The return structure of the separately-listed unmatched events remains under-specified, which is the main remaining gap.

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 nothing for the description to disambiguate; the empty schema is fully self-explanatory. Baseline 4 applies.

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?

States a specific verb+resource: 'Discover PGA tournament URL contexts', and pins down the returned fields (year, slug, ID) as coming from actual main-tour schedule/sitemap links. It is clearly a context-resolver rather than one of the pgatour_tournament_<tab> data tools, though it never names a sibling to contrast against.

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?

'Use returned contexts with tournament tab endpoints' gives an explicit downstream usage, effectively telling the agent this is a prerequisite resolver for the tab tools. It also warns that events without a source link are listed separately so slugs should not be guessed, but it offers no explicit when-not-to-use guidance or statement of what to do if a tournament is missing.

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

Deploy Server

Other Tools