Skip to main content
Glama
kureha4

HowToCook-MCP Server

by kureha4

mcp_howtocook_getAllRecipes

Retrieve all recipes from a Chinese cooking database to help users find meal ideas, plan weekly menus, and solve the "what to eat today" problem.

Instructions

获取所有菜谱

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
no_paramNo无参数

Implementation Reference

  • Executes the tool logic: simplifies all recipes to name and description only, stringifies to JSON, and returns in MCP content format.
    async () => {
      // 返回更简化版的菜谱数据,只包含name和description
      const simplifiedRecipes = recipes.map(simplifyRecipeNameOnly);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(simplifiedRecipes, null, 2),
          },
        ],
      };
    }
  • Input schema using Zod: optional string parameter 'no_param'.
    {
      'no_param': z.string().optional()
                       .describe('无参数')
    },
  • Registers the tool on the MCP server with name, description, input schema, and handler function.
    server.tool(
      "mcp_howtocook_getAllRecipes",
      "获取所有菜谱",
      {
        'no_param': z.string().optional()
                         .describe('无参数')
      },
      async () => {
        // 返回更简化版的菜谱数据,只包含name和description
        const simplifiedRecipes = recipes.map(simplifyRecipeNameOnly);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(simplifiedRecipes, null, 2),
            },
          ],
        };
      }
    );
  • src/index.ts:56-56 (registration)
    Invokes the registration function during server instance creation, passing the server and loaded recipes.
    registerGetAllRecipesTool(server, recipes);
  • Utility function that simplifies a Recipe to just name and description, used in the tool handler.
    export function simplifyRecipeNameOnly(recipe: Recipe): NameOnlyRecipe {
      return {
        name: recipe.name,
        description: recipe.description
      };
    }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It doesn't disclose whether this is a read-only operation, potential rate limits, error conditions, or return format (e.g., list structure). '获取所有菜谱' suggests a safe read, but lacks details needed for reliable use.

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

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('获取所有菜谱') but under-specified rather than efficiently informative. It's front-loaded but lacks necessary context, making it more of a placeholder than a well-structured summary that earns its brevity.

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?

For a tool with no annotations, no output schema, and minimal description, this is incomplete. The agent won't know what the return value looks like (e.g., list of recipes with fields), potential limitations, or how it differs from siblings beyond name. More context is needed for effective use.

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 1 parameter with 100% coverage (no_param described as '无参数' - no parameter), and the description doesn't add parameter details. Since there are effectively 0 functional parameters, the baseline is 4—the description doesn't need to compensate, and the schema adequately handles the trivial case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取所有菜谱' (Get all recipes) states a basic action but is vague about scope and format. It doesn't specify whether this returns a complete list, paginated results, or what 'all' means in context. While it distinguishes from siblings by not filtering (vs. getRecipeById, getRecipesByCategory), it lacks the specificity needed for a 4-5 score.

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 like getRecipesByCategory or recommendMeals. The description implies a broad retrieval but doesn't mention trade-offs (e.g., performance for large datasets) or prerequisites, leaving the agent to guess based on tool names alone.

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/kureha4/mcptest1'

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