Skip to main content
Glama

find_attractions

Search Disney park attractions with filters for height requirements, Lightning Lane availability, thrill level, and single rider lines to plan your visit effectively.

Instructions

Find attractions at Disney parks with filters. Returns ride metadata including height requirements, Lightning Lane status, thrill level, and single rider availability. Use list_parks first to get valid destination and park IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationYesDestination ID: 'wdw' (Walt Disney World) or 'dlr' (Disneyland Resort)
parkIdNoFilter to a specific park by ID (e.g., '80007944' for Magic Kingdom). Get park IDs from list_parks.
filtersNoOptional filters to narrow results

Implementation Reference

  • The async handler function that executes the find_attractions tool logic, including validation, fetching attractions via client, applying filters, formatting, and returning structured response.
    export const handler: ToolHandler = async (args) => {
      return withTimeout(
        "find_attractions",
        async () => {
          // Validate destination
          const destination = args.destination as string | undefined;
          if (!destination || !["wdw", "dlr"].includes(destination)) {
            return formatErrorResponse(
              new ValidationError("destination must be 'wdw' or 'dlr'", "destination", destination)
            );
          }
    
          const parkId = args.parkId as string | undefined;
          const filters = (args.filters as Record<string, unknown>) ?? {};
    
          try {
            const client = getDisneyFinderClient();
            let attractions = await client.getAttractions(destination as DestinationId, parkId);
    
            // Apply filters
            attractions = applyFilters(attractions, filters);
    
            return {
              content: [
                {
                  type: "text" as const,
                  text: JSON.stringify(
                    {
                      destination,
                      parkId: parkId ?? null,
                      count: attractions.length,
                      attractions: attractions.map(formatAttraction),
                    },
                    null,
                    2
                  ),
                },
              ],
            };
          } catch (error) {
            return formatErrorResponse(error);
          }
        },
        TIMEOUTS.DEFAULT
      );
    };
  • ToolDefinition object defining the name, description, and inputSchema (including properties for destination, parkId, and filters) for the find_attractions tool.
    export const definition: ToolDefinition = {
      name: "find_attractions",
      description:
        "Find attractions at Disney parks with filters. " +
        "Returns ride metadata including height requirements, Lightning Lane status, " +
        "thrill level, and single rider availability. " +
        "Use list_parks first to get valid destination and park IDs.",
      inputSchema: {
        type: "object" as const,
        properties: {
          destination: {
            type: "string",
            description: "Destination ID: 'wdw' (Walt Disney World) or 'dlr' (Disneyland Resort)",
            enum: ["wdw", "dlr"],
          },
          parkId: {
            type: "string",
            description:
              "Filter to a specific park by ID (e.g., '80007944' for Magic Kingdom). " +
              "Get park IDs from list_parks.",
          },
          filters: {
            type: "object",
            description: "Optional filters to narrow results",
            properties: {
              hasLightningLane: {
                type: "boolean",
                description: "Only show attractions with Lightning Lane",
              },
              maxHeightRequirement: {
                type: "number",
                description: "Maximum height requirement in inches (e.g., 40 for kids)",
              },
              thrillLevel: {
                type: "string",
                description: "Filter by thrill level",
                enum: ["family", "moderate", "thrill"],
              },
              hasSingleRider: {
                type: "boolean",
                description: "Only show attractions with single rider line",
              },
            },
          },
        },
        required: ["destination"],
      },
    };
  • Registration of the find_attractions tool (via attractions.definition and attractions.handler) in the central tools array used by registerTools function.
    const tools: ToolEntry[] = [
      { definition: destinations.definition, handler: destinations.handler },
      { definition: attractions.definition, handler: attractions.handler },
      { definition: dining.definition, handler: dining.handler },
      { definition: search.definition, handler: search.handler },
      { definition: discover.definition, handler: discover.handler },
      { definition: status.definition, handler: status.handler },
      { definition: sync.definition, handler: sync.handler },
    ];
  • Helper function that filters the attractions list based on Lightning Lane, height requirements, thrill level, and single rider options.
    function applyFilters(
      attractions: DisneyAttraction[],
      filters: Record<string, unknown>
    ): DisneyAttraction[] {
      return attractions.filter((attr) => {
        // Lightning Lane filter
        if (filters.hasLightningLane === true) {
          if (!attr.lightningLane?.available) return false;
        }
    
        // Height requirement filter
        if (typeof filters.maxHeightRequirement === "number") {
          const maxHeight = filters.maxHeightRequirement;
          if (attr.heightRequirement && attr.heightRequirement.inches > maxHeight) {
            return false;
          }
        }
    
        // Thrill level filter
        if (filters.thrillLevel) {
          if (attr.thrillLevel !== filters.thrillLevel) return false;
        }
    
        // Single rider filter
        if (filters.hasSingleRider === true) {
          if (!attr.singleRider) return false;
        }
    
        return true;
      });
    }
  • Helper function that formats a raw DisneyAttraction object into a structured response format with metadata, features, accessibility, and tags.
    function formatAttraction(attr: DisneyAttraction): {
      id: string;
      name: string;
      slug: string | null;
      park: string | null;
      location: { latitude: number; longitude: number } | null;
      url: string | null;
      metadata: {
        heightRequirement: string | null;
        thrillLevel: string | null;
        experienceType: string | null;
        duration: string | null;
      };
      features: {
        lightningLane: string;
        singleRider: boolean;
        riderSwap: boolean;
        photopass: boolean;
        virtualQueue: boolean;
      };
      accessibility: {
        wheelchairAccessible: boolean;
      };
      tags: string[];
    } {
      return {
        id: attr.id,
        name: attr.name,
        slug: attr.slug,
        park: attr.parkName,
        location: attr.location,
        url: attr.url,
        metadata: {
          heightRequirement: attr.heightRequirement?.description ?? null,
          thrillLevel: attr.thrillLevel,
          experienceType: attr.experienceType,
          duration: attr.duration,
        },
        features: {
          lightningLane: attr.lightningLane?.tier ?? "none",
          singleRider: attr.singleRider,
          riderSwap: attr.riderSwap,
          photopass: attr.photopass,
          virtualQueue: attr.virtualQueue,
        },
        accessibility: {
          wheelchairAccessible: attr.wheelchairAccessible,
        },
        tags: attr.tags,
      };
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what the tool returns (ride metadata with specific attributes) and implies a read-only operation by using 'Find' and 'Returns,' but it doesn't mention potential limitations like rate limits, authentication needs, or error conditions. The description adds some context about the return data but lacks comprehensive behavioral traits.

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

Conciseness5/5

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

The description is front-loaded with the core purpose in the first sentence, followed by return details and usage guidance. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-structured.

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?

Given the complexity (3 parameters with nested objects, no annotations, no output schema), the description is reasonably complete. It covers the purpose, return data, and usage prerequisites. However, it could improve by addressing potential behavioral aspects like error handling or data freshness, which are not covered by annotations or output schema.

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 100%, so the input schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'filters' generically and referencing 'list_parks' for IDs, but it doesn't provide additional syntax, format details, or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the specific action ('Find attractions at Disney parks with filters') and resource ('attractions'), distinguishing it from siblings like 'find_dining' or 'list_parks'. It specifies the exact type of metadata returned (ride metadata including height requirements, Lightning Lane status, thrill level, and single rider availability), making the purpose highly specific and differentiated.

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

Usage Guidelines5/5

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

The description explicitly states 'Use list_parks first to get valid destination and park IDs,' providing clear prerequisites and guidance on when to use this tool versus alternatives. It distinguishes this tool from 'list_parks' by indicating that 'list_parks' should be used first to obtain necessary IDs, establishing a clear workflow.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cameronsjo/mouse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server