Skip to main content
Glama
WhenYouAreStrange

goodbook-mcp

find_recipe_standards

Find standardized recipes and preparation methods for specific dishes using food service PDF guidelines.

Instructions

Find standardized recipes and preparation methods for specific dishes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dish_nameYesName of the dish to find recipe standards for
cuisine_typeNo

Implementation Reference

  • Core handler function executing the tool logic: generates search terms based on dish_name and optional cuisine_type, searches PDF content via pdfParser, deduplicates results, and formats a text response with up to 8 standards.
    async function findRecipeStandards(dish_name, cuisine_type) {
      const recipeTerms = [
        dish_name,
        `рецепт ${dish_name}`,
        `стандарт ${dish_name}`,
        `приготовление ${dish_name}`,
        `recipe ${dish_name}`,
        `standard ${dish_name}`,
        `preparation ${dish_name}`
      ];
    
      if (cuisine_type) {
        recipeTerms.push(`${cuisine_type} ${dish_name}`);
      }
    
      let allResults = [];
      for (const term of recipeTerms) {
        const results = pdfParser.searchContent(term);
        if (results.results) {
          allResults.push(...results.results);
        }
      }
    
      const uniqueResults = allResults.filter((result, index, self) => 
        index === self.findIndex(r => r.content === result.content)
      );
    
      let response = `Recipe standards for "${dish_name}"`;
      if (cuisine_type) response += ` (${cuisine_type} cuisine)`;
      response += ":\n\n";
      
      if (uniqueResults.length === 0) {
        response += "No specific recipe standards found for this dish.";
      } else {
        uniqueResults.slice(0, 8).forEach((result, index) => {
          response += `Standard ${index + 1}:\n`;
          response += `${result.content}\n\n`;
        });
      }
    
      return {
        content: [{
          type: "text",
          text: response
        }]
      };
    }
  • Zod schema for input validation of the tool's parameters: dish_name (required string) and cuisine_type (optional string). Converted to JSON schema for MCP.
    const findRecipeStandardsSchema = z.object({
      dish_name: z.string().describe("Name of the dish to find recipe standards for"),
      cuisine_type: z.string().optional().describe("Optional: type of cuisine or cooking style"),
    });
  • src/index.js:197-200 (registration)
    Tool registration in the toolDefinitions array, including name, description, and inputSchema derived from Zod schema.
      name: "find_recipe_standards",
      description: "Find standardized recipes and preparation methods for specific dishes",
      inputSchema: zodToJsonSchema(findRecipeStandardsSchema)
    }
  • Alternative class method handler for the tool logic in GoodbookTools class (nearly identical to index.js implementation).
    async findRecipeStandards(dishName, cuisineType = null) {
      const recipeTerms = [
        dishName,
        `рецепт ${dishName}`,
        `стандарт ${dishName}`,
        `приготовление ${dishName}`,
        `recipe ${dishName}`,
        `standard ${dishName}`,
        `preparation ${dishName}`
      ];
    
      if (cuisineType) {
        recipeTerms.push(`${cuisineType} ${dishName}`);
      }
    
      let allResults = [];
      for (const term of recipeTerms) {
        const results = this.pdfParser.searchContent(term);
        if (results.results) {
          allResults.push(...results.results);
        }
      }
    
      const uniqueResults = allResults.filter((result, index, self) => 
        index === self.findIndex(r => r.content === result.content)
      );
    
      let response = `Recipe standards for "${dishName}"`;
      if (cuisineType) response += ` (${cuisineType} cuisine)`;
      response += ":\n\n";
      
      if (uniqueResults.length === 0) {
        response += "No specific recipe standards found for this dish.";
      } else {
        uniqueResults.slice(0, 8).forEach((result, index) => {
          response += `Standard ${index + 1}:\n`;
          response += `${result.content}\n\n`;
        });
      }
    
      return {
        content: [{
          type: "text",
          text: response
        }]
      };
    }
  • src/tools.js:97-112 (registration)
    Tool definition/registration in GoodbookTools.getToolDefinitions(), with inline JSON schema.
    name: "find_recipe_standards",
    description: "Find standardized recipes and preparation methods for specific dishes",
    inputSchema: {
      type: "object",
      properties: {
        dish_name: {
          type: "string",
          description: "Name of the dish to find recipe standards for"
        },
        cuisine_type: {
          type: "string",
          description: "Optional: type of cuisine or cooking style"
        }
      },
      required: ["dish_name"]
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'finds' information, implying a read-only operation, but doesn't address critical aspects like whether it requires authentication, has rate limits, returns structured data, or handles errors. This leaves significant gaps in understanding how the tool behaves.

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

Conciseness4/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's appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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 for a tool with two parameters. It doesn't explain what the tool returns (e.g., recipe details, preparation steps), how results are formatted, or any behavioral traits, making it inadequate for full contextual understanding.

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 implies parameters related to dishes but doesn't detail them beyond 'specific dishes'. With 50% schema description coverage (one parameter documented, one not), the description adds minimal value over the schema, which already documents 'dish_name' well. It doesn't compensate for the undocumented 'cuisine_type' parameter.

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 tool's purpose with specific verbs ('find standardized recipes and preparation methods') and resources ('for specific dishes'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'search_food_standards' or 'get_cooking_guidelines', which might have overlapping functionality.

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. It doesn't mention any prerequisites, exclusions, or specific contexts for usage, leaving the agent to infer based on tool names alone without explicit direction.

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/WhenYouAreStrange/goodbook-mcp'

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