Skip to main content
Glama

search_tee_times

Read-only

Search recently cached tee times for up to 50 selected courses on one date. A cache miss is not proof of no availability. After a miss, retry with refresh=true and at most three course IDs to request fresh inventory.

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": {
      "region": "<region>",
      "date": "<date>",
      "courseIds": "<courseIds>",
      "players": "<players>"
    },
    "name": "search_tee_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesLocal date in YYYY-MM-DD format, within the next 31 days
holesNo
limitNo
regionYes
playersYes
refreshNoRefresh missing or stale inventory for at most three selected courses.
maxPriceNo
toMinuteNo
courseIdsYes
fromMinuteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), and the description adds the non-obvious behavior that results come from a cache, that misses are inconclusive, and that refresh is capped at three courses. That is exactly the context an agent could not infer from structured fields.

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?

Two tightly written sentences with the scope first and the recovery rule second; nothing is wasted. Slightly terse for the amount of undocumented parameters, but the structure is front-loaded and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, 4-required tool with no output schema and low schema coverage, the description covers the caching/retry model well but says nothing about what a result contains or how the region, players, and price filters behave. Adequate, not complete.

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 only 20%, so the description must carry the load. It clarifies refresh semantics and the three-course cap plus the 50-course scope, but leaves region, players, holes, limit, maxPrice, and the minute-range fields to bare numeric bounds with no meaning added.

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 verb and resource ('Search recently cached tee times') plus concrete scope: up to 50 courses, one date. The 'cached' qualifier distinguishes this from a live-inventory fetch and tells the agent what kind of data it is reading.

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?

Gives explicit recovery protocol: a cache miss is not proof of no availability, so retry with refresh=true on at most three course IDs. That is real when/how guidance, though it never says when to prefer a sibling such as create_tee_time_poll or prepare_alert instead.

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