Skip to main content
Glama
Kong

For Five Coffee MCP Server

by Kong

get_full_menu

Fetch the complete menu from For Five Coffee café, including all categories and items, to access detailed menu information.

Instructions

Fetch the complete menu from For Five Coffee including all categories and items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_full_menu' tool. Fetches complete menu data from cache/API/Puppeteer/static scrape and returns structured JSON in MCP text content format.
    async getFullMenu() {
      const menuData = await this.fetchMenuData();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                restaurant: 'For Five Coffee',
                totalItems: menuData.items.length,
                categories: menuData.categories,
                items: menuData.items,
                lastUpdated: menuData.lastUpdated,
                cached: menuData.cached || false,
                source: menuData.source || 'puppeteer',
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • server.js:98-127 (registration)
    MCP stdio server registration for CallToolRequestSchema, dispatching 'get_full_menu' to this.getFullMenu() handler.
      this.server.setRequestHandler(CallToolRequestSchema, async request => {
        const { name, arguments: args } = request.params;
    
        try {
          switch (name) {
            case 'get_full_menu':
              return await this.getFullMenu();
            case 'search_menu_items':
              return await this.searchMenuItems(args.query);
            case 'get_menu_categories':
              return await this.getMenuCategories();
            case 'get_items_by_category':
              return await this.getItemsByCategory(args.category);
            case 'clear_menu_cache':
              return await this.clearMenuCache();
            default:
              throw new Error(`Unknown tool: ${name}`);
          }
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error: ${error.message}`,
              },
            ],
          };
        }
      });
    }
  • server.js:40-96 (registration)
    MCP stdio server registration for ListToolsRequestSchema, defining the 'get_full_menu' tool with its schema.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'get_full_menu',
          description:
            'Fetch the complete menu from For Five Coffee including all categories and items',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        },
        {
          name: 'search_menu_items',
          description: 'Search for specific menu items by name or category',
          inputSchema: {
            type: 'object',
            properties: {
              query: {
                type: 'string',
                description: 'Search term to find in menu items (name, description, or category)',
              },
            },
            required: ['query'],
          },
        },
        {
          name: 'get_menu_categories',
          description: 'Get all available menu categories',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        },
        {
          name: 'get_items_by_category',
          description: 'Get all menu items from a specific category',
          inputSchema: {
            type: 'object',
            properties: {
              category: {
                type: 'string',
                description: 'The category name to filter by',
              },
            },
            required: ['category'],
          },
        },
        {
          name: 'clear_menu_cache',
          description: 'Clear the menu cache to force fresh data on next request',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        },
      ],
    }));
  • Input schema definition for the 'get_full_menu' tool (no required parameters).
    {
      name: 'get_full_menu',
      description:
        'Fetch the complete menu from For Five Coffee including all categories and items',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions fetching data but doesn't specify whether this is a read-only operation, potential rate limits, authentication requirements, or what the return format looks like (e.g., structure of categories and items). For a tool with zero annotation coverage, this leaves significant behavioral 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 a single, efficient sentence that front-loads the key information ('Fetch the complete menu') and adds necessary detail ('including all categories and items') without any wasted words. It's appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimally adequate but lacks depth. It doesn't explain the return structure (e.g., how categories and items are organized), which would be helpful since no output schema exists. For a tool fetching complex menu data, more contextual detail about the response would improve completeness.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here since no parameters exist. A baseline score of 4 is given as the description doesn't need to compensate for any parameter documentation gaps.

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 clearly states the action ('Fetch') and target resource ('complete menu from For Five Coffee including all categories and items'), making the tool's purpose immediately understandable. It distinguishes itself from siblings by specifying 'complete menu' rather than filtered subsets, though it doesn't explicitly name the sibling tools for comparison.

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?

The description implies usage context by specifying 'complete menu' versus filtered options, suggesting this tool is for retrieving all data at once rather than subsets. However, it doesn't explicitly state when to use this versus alternatives like 'get_menu_categories' or 'search_menu_items', leaving some ambiguity about optimal use cases.

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/Kong/for-five-mcp'

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