Seatac Connection rides

Find things to do in Seattle

find_things_to_do

Read-onlyIdempotent

Seattle experiences the trip planner offers (Space Needle and Chihuly Garden, a harbor cruise, the Museum of Flight, food tours and more): what each is, how long it takes, which parts of the day it fits, rough price level, where it is, a ticket link, and with hotel_slug about how long it takes to get there. Each has a pick_id to pass to plan_seattle_trip's picks.

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

Input Schema

Name	Required	Description
`part`	No	Only those that fit this part of the day.
`limit`	No	How many (default 10).
`hotel_slug`	No	Our hotel (from plan_seattle_trip's hotel_options) to estimate travel time from.

Output Schema

Name	Required	Description	Default
`error`	No
`page_url`	No
`experiences`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds that passing hotel_slug yields travel-time estimates and that each item carries a pick_id for downstream planning, but it does not mention filtering behavior, ordering, or what happens when part/limit interact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is one long parenthetical-laden sentence that is hard to parse and buries the pick_id handoff at the very end. The information is useful but the structure impedes scanning; it should have been split into purpose, contents, and integration sentences.

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 an output schema present and full parameter documentation, the description supplies the missing integration context: what an experience record contains and that pick_id feeds plan_seattle_trip's picks. What remains thin is sibling differentiation among the other find_* tools.

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 all three parameters are already documented in the schema, including the enum for part and the travel-time role of hotel_slug. The description restates that hotel_slug produces travel time and that records fit parts of the day, adding little beyond the schema. 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 names the resource concretely (Seattle experiences offered by the trip planner: Space Needle, harbor cruise, Museum of Flight, food tours) and enumerates what each record contains. An agent can distinguish this from find_restaurants or find_events_near by the 'trip planner experiences' framing. The verb itself is only implied by the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the workflow link ('pick_id to pass to plan_seattle_trip's picks'), which tells the agent this feeds trip planning. However, there is no explicit statement of when to use this versus find_events_near, find_restaurants, or find_cruise_sailings, and no exclusions.

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?