Skip to main content
Glama

find_dining

Search for Disney park restaurants using filters like cuisine, meal period, price range, and reservation options to find dining locations matching specific preferences.

Instructions

Find dining locations at Disney parks with filters. Returns restaurant metadata including service type, meal periods, cuisine, price range, and reservation requirements. 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. Get park IDs from list_parks.
filtersNoOptional filters to narrow results

Implementation Reference

  • Main execution logic for the find_dining tool: validates destination, fetches dining data from DisneyFinderClient, applies user filters, formats output as JSON.
    export const handler: ToolHandler = async (args) => {
      return withTimeout(
        "find_dining",
        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 dining = await client.getDining(destination as DestinationId, parkId);
    
            // Apply filters
            dining = applyFilters(dining, filters);
    
            return {
              content: [
                {
                  type: "text" as const,
                  text: JSON.stringify(
                    {
                      destination,
                      parkId: parkId ?? null,
                      count: dining.length,
                      dining: dining.map(formatDining),
                    },
                    null,
                    2
                  ),
                },
              ],
            };
          } catch (error) {
            return formatErrorResponse(error);
          }
        },
        TIMEOUTS.DEFAULT
      );
    };
  • Tool definition including name, description, and detailed input schema for parameters like destination, parkId, and filters.
    export const definition: ToolDefinition = {
      name: "find_dining",
      description:
        "Find dining locations at Disney parks with filters. " +
        "Returns restaurant metadata including service type, meal periods, " +
        "cuisine, price range, and reservation requirements. " +
        "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. Get park IDs from list_parks.",
          },
          filters: {
            type: "object",
            description: "Optional filters to narrow results",
            properties: {
              serviceType: {
                type: "string",
                description: "Filter by service type",
                enum: [
                  "table-service",
                  "quick-service",
                  "character-dining",
                  "fine-signature-dining",
                  "lounge",
                ],
              },
              mealPeriod: {
                type: "string",
                description: "Filter to restaurants serving this meal",
                enum: ["breakfast", "lunch", "dinner", "snacks"],
              },
              reservationsAccepted: {
                type: "boolean",
                description: "Only show restaurants that accept reservations",
              },
              characterDining: {
                type: "boolean",
                description: "Only show character dining experiences",
              },
              mobileOrder: {
                type: "boolean",
                description: "Only show restaurants with mobile ordering",
              },
            },
          },
        },
        required: ["destination"],
      },
    };
  • Registers the find_dining tool (via dining.definition and dining.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 to filter the dining list based on provided filter criteria such as serviceType, mealPeriod, etc.
    function applyFilters(dining: DisneyDining[], filters: Record<string, unknown>): DisneyDining[] {
      return dining.filter((d) => {
        // Service type filter
        if (filters.serviceType) {
          if (d.serviceType !== filters.serviceType) return false;
        }
    
        // Meal period filter
        if (filters.mealPeriod) {
          if (!d.mealPeriods.includes(filters.mealPeriod as MealPeriod)) return false;
        }
    
        // Reservations filter
        if (filters.reservationsAccepted === true) {
          if (!d.reservationsAccepted) return false;
        }
    
        // Character dining filter
        if (filters.characterDining === true) {
          if (!d.characterDining) return false;
        }
    
        // Mobile order filter
        if (filters.mobileOrder === true) {
          if (!d.mobileOrder) return false;
        }
    
        return true;
      });
    }
  • Helper function to format individual dining entries for the response, mapping raw data to a clean output structure.
    function formatDining(d: DisneyDining): {
      id: string;
      name: string;
      slug: string | null;
      park: string | null;
      location: { latitude: number; longitude: number } | null;
      url: string | null;
      metadata: {
        serviceType: string | null;
        priceRange: string | null;
        cuisine: string[];
        mealPeriods: string[];
      };
      features: {
        reservationsAccepted: boolean;
        reservationsRequired: boolean;
        mobileOrder: boolean;
        characterDining: boolean;
        disneyDiningPlan: boolean;
      };
    } {
      return {
        id: d.id,
        name: d.name,
        slug: d.slug,
        park: d.parkName,
        location: d.location,
        url: d.url,
        metadata: {
          serviceType: d.serviceType,
          priceRange: d.priceRange?.symbol ?? null,
          cuisine: d.cuisineTypes,
          mealPeriods: d.mealPeriods,
        },
        features: {
          reservationsAccepted: d.reservationsAccepted,
          reservationsRequired: d.reservationsRequired,
          mobileOrder: d.mobileOrder,
          characterDining: d.characterDining,
          disneyDiningPlan: d.disneyDiningPlan,
        },
      };
    }
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. It discloses the return format (restaurant metadata with specific fields) and hints at filtering behavior, but lacks details on rate limits, error handling, pagination, or authentication needs. For a tool with no annotations, this is a moderate disclosure—adequate but with gaps.

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, followed by return details and a usage guideline. Both sentences earn their place—the first defines the tool, and the second provides critical context. It's efficient with zero waste, making it highly concise 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 no annotations and no output schema, the description does well by specifying return metadata and prerequisites. However, it lacks details on behavioral aspects like rate limits or error handling. For a tool with 3 parameters and nested objects, it's mostly complete but could improve by addressing missing behavioral transparency.

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 schema already documents all parameters thoroughly. The description adds minimal value beyond the schema, mentioning filters generally but not elaborating on parameter usage. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 dining locations at Disney parks with filters') and resource ('restaurant metadata'), distinguishing it from siblings like find_attractions (which focuses on attractions rather than dining) and list_parks (which lists parks rather than restaurants). It provides a comprehensive list of what metadata is returned, making the purpose explicit 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 doesn't mention other siblings like search or discover, but the specific instruction for list_parks as a prerequisite is sufficient for a top score.

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