Skip to main content
Glama
Kong

For Five Coffee MCP Server

by Kong

get_menu_categories

Retrieve all menu categories from For Five Coffee café to organize and navigate available food and beverage options.

Instructions

Get all available menu categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main execution function for the 'get_menu_categories' tool. Fetches the menu data (from cache or live sources) and returns a JSON response containing all available menu categories and the total count.
    async getMenuCategories() {
      const menuData = await this.fetchMenuData();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                categories: menuData.categories,
                totalCategories: menuData.categories.length,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • The input schema for the tool, specifying an empty object (no parameters required). Part of the tool definition in the MCP ListTools response.
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • server.js:65-72 (registration)
    Tool registration in the MCP ListToolsRequestSchema handler, defining the tool's name, description, and schema for discovery.
    {
      name: 'get_menu_categories',
      description: 'Get all available menu categories',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • server.js:107-108 (registration)
    Tool dispatch registration in the MCP CallToolRequestSchema switch statement, routing calls to the handler function.
    case 'get_menu_categories':
      return await this.getMenuCategories();
  • server.js:324-325 (registration)
    Additional tool dispatch registration in the HTTP /mcp endpoint's tools/call handler.
    case 'get_menu_categories':
      result = await this.getMenuCategories();
Behavior2/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 states the tool retrieves categories but doesn't mention aspects like whether it's read-only, requires authentication, has rate limits, or what the return format looks like (e.g., list structure). This leaves significant gaps for an agent to understand its behavior.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 'all available menu categories' entails (e.g., format, pagination, or filtering), and with no structured data to fall back on, an agent would have insufficient context to use the tool effectively beyond its basic purpose.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds no parameter information, which is appropriate here, but doesn't compensate for any gaps since there are none. A baseline of 4 is given as it meets minimal requirements without redundancy.

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 ('Get') and resource ('all available menu categories'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_full_menu' or 'get_items_by_category', which might also retrieve menu-related data but with different scopes or filters.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_full_menu' (which might include items) or 'get_items_by_category' (which filters by category). The description implies it retrieves categories only, but lacks explicit comparisons or exclusions for sibling tools.

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