Skip to main content
Glama
Kong

For Five Coffee MCP Server

by Kong

search_menu_items

Find menu items by name or category to quickly locate specific drinks and food offerings from For Five Coffee café.

Instructions

Search for specific menu items by name or category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term to find in menu items (name, description, or category)

Implementation Reference

  • Core handler function for 'search_menu_items' tool. Fetches menu data, filters items matching the query in name, description, or category, and returns structured JSON response.
    async searchMenuItems(query) {
      const menuData = await this.fetchMenuData();
      const searchTerm = query.toLowerCase();
    
      const results = menuData.items.filter(
        item =>
          item.name.toLowerCase().includes(searchTerm) ||
          item.description.toLowerCase().includes(searchTerm) ||
          item.category.toLowerCase().includes(searchTerm)
      );
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                query,
                resultsFound: results.length,
                items: results,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Input schema validation for the tool, requiring a 'query' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search term to find in menu items (name, description, or category)',
        },
      },
      required: ['query'],
    },
  • server.js:51-64 (registration)
    Registration of the 'search_menu_items' tool in the MCP ListToolsRequestSchema handler, including name, description, and schema.
    {
      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'],
      },
    },
  • server.js:105-106 (registration)
    Dispatch/registration case in the CallToolRequestSchema handler that invokes the searchMenuItems method.
    case 'search_menu_items':
      return await this.searchMenuItems(args.query);
  • server.js:278-288 (registration)
    Secondary registration of the tool in the HTTP JSON-RPC /mcp tools/list response.
    {
      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' },
        },
        required: ['query'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, how results are returned (e.g., pagination, sorting), error handling, or any constraints like rate limits, which is inadequate for a search tool.

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 with zero waste, clearly front-loading the tool's purpose. Every word earns its place, making it appropriately sized and well-structured for quick understanding.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the search returns (e.g., list of items, error formats), behavioral aspects, or how it differs from siblings, leaving gaps in understanding for an AI agent despite the simple parameter 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?

The description adds minimal meaning beyond the input schema, which has 100% coverage and fully documents the single 'query' parameter. The description implies the query searches across name, description, or category, but the schema already states this, so it doesn't compensate significantly. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('search') and resource ('menu items') with specific criteria ('by name or category'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_items_by_category' or 'get_full_menu', which limits its score to 4 instead of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_items_by_category' or 'get_full_menu'. It mentions searching 'by name or category' but doesn't clarify if this is for filtered queries versus retrieving all items, leaving usage context implied at best.

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