Seatac Connection rides

Find Seattle events near a place

find_events_near

Read-onlyIdempotent

Find Seattle-area games, concerts and shows on given dates (from Seatac's daily Ticketmaster snapshot), the same list seatac.co shows as "Happening while you're here". With near (the airport, a cruise pier, or a hotel area) events are nearest first, one per venue, within 20 miles, with the straight-line distance; without it, the biggest events first. Each event has its start time, the planned ride (pickup time to arrive 45 minutes early, estimated end, ride back), a prefilled round-trip booking link, the event page and the ticket link.

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": {
      "from": "<from>"
    },
    "name": "find_events_near"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last date, inclusive (up to 14 days after from). Omit for one day.
`from`	Yes	First date, YYYY-MM-DD (Seattle).
`kind`	No	Only sports, concert, or show.
`near`	No	Where the traveler is: sea-airport, a cruise pier, or a hotel area. Omit for the biggest events.
`limit`	No	Events to return (1-10, default 5).
`ride_from`	No	Optional address the ride to the event starts from (e.g. their hotel), prefilled in the booking link.

Output Schema

Name	Required	Description	Default
`error`	No
`events`	No
`page_url`	No
`searched`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/closed-world safety profile, and the description adds genuine behavioral context: data freshness (daily snapshot), the 20-mile radius ceiling, deduplication to one event per venue, and the enrichment returned (ride plan with 45-minute-early pickup, prefilled booking link). No contradiction with annotations.

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 purpose and, importantly, the mode-switching rule early. Dense but readable; the final sentence enumerating return fields partially duplicates the output schema, which is mild waste rather than bloat.

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

Completeness5/5

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

Given an output schema and full annotations, the description supplies everything an agent needs to choose it: data source, geographic constraint, ordering modes, enrichment contents, and the date-range scope. Nothing material is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond the schema by explaining the consequence of supplying `near` (ordering, per-venue dedupe, distance, 20-mile cutoff) and tying `ride_from` to the prefilled booking link. It doesn't restate the date-range or limit semantics, which the schema handles.

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?

Specific verb+resource with scope: 'Find Seattle-area games, concerts and shows on given dates,' plus the data provenance ('Seatac's daily Ticketmaster snapshot'). Clearly distinguishable from siblings like find_cruise_sailings, recommend_hotels_with_rides, and quote_ride, which cover different resources.

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 states the with-near vs without-near behavior ('nearest first... within 20 miles' vs 'biggest events first'), which effectively tells the agent which mode to pick. It does not explicitly name sibling alternatives or exclusions, keeping it just below a 5.

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

All Seatac Connection rides tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?