Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pgatour_schedule_seasons

Discover PGA Tour schedule seasons and return each native season value with its display label for a selected tour, so you can pass valid options to the schedule season selector.

Instructions

Discover PGA tour-specific schedule seasons. Returns every native season value and display label for the selected tour. Labels such as2022–2023 are not replaced by guessed calendar years. Use returned values with the schedule season selector; omission there preserves its own source default.

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

Input Schema

NameRequiredDescriptionDefault
tourNoNative tour, defaultR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/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 behavioral burden. It does disclose a meaningful trait beyond the schema—that native labels like "2022–2023" are passed through rather than normalized to calendar years—which is real value, but it never states that this is a safe read-only operation, whether results are paginated, or what the response container 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?

The scope and the key caveat about labels are front-loaded, and each sentence contributes something. Minor defects (missing space in "such as2022–2023", and the return-value nuance taking three sentences) keep it from a 5.

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 usefully compensates by describing the returned value/label pair and warning against year normalization. For a one-optional-param lookup tool it is nearly sufficient; only the response shape and read-only nature are left unstated.

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%, with the single tour parameter already enum-constrained and documented as defaulting to R. The description only refers to "the selected tour" and adds no meaning about what the four tour codes denote or how they change the returned season set, so baseline 3 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?

The description pairs a specific verb ("Discover") with a precisely scoped resource ("PGA tour-specific schedule seasons") and states what is returned: every native season value plus display label. It implicitly separates itself from the schedule tool by positioning this as a value source for the schedule season selector, though it never names the sibling explicitly.

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?

It gives actionable routing guidance: use the returned values with "the schedule season selector," and notes that omitting that selector preserves its source default. That covers the use case and the do-nothing case, but offers no explicit exclusion or situation where this tool should not be called.

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