Skip to main content
Glama
Sign In
HowToCook-MCP Server

HowToCook-MCP Server

by worryzyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mcp_howtocook_getAllRecipes

Retrieve all available recipes from the HowToCook repository to assist with meal planning and recipe recommendations for AI-powered personal chefs.

Instructions

获取所有菜谱

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp_howtocook_getAllRecipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
no_paramNo无参数

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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. It only states the action without disclosing behavioral traits such as whether this is a read-only operation, potential rate limits, pagination, or what the return format might be. For a tool with no annotations, this is a significant gap in transparency.

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 phrase '获取所有菜谱', which is extremely concise and front-loaded with the core action. There is no wasted text, making it efficient 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 'all recipes' includes (e.g., format, limits) or behavioral aspects. For a tool with no structured data to rely on, the description should provide more context to be fully helpful.

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, describing it as '无参数' (no parameter). The description doesn't add meaning beyond the schema, but since the parameter indicates no input is needed, the baseline is high. The description implicitly aligns with this by not mentioning parameters, but it doesn't provide extra context.

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

Purpose3/5

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

The description '获取所有菜谱' (Get all recipes) states the basic action and resource but lacks specificity. It doesn't distinguish from siblings like 'mcp_howtocook_getRecipesByCategory' or 'mcp_howtocook_getRecipeById' by explaining scope or filtering differences. The purpose is clear but vague regarding what 'all' entails.

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. It doesn't mention siblings like 'mcp_howtocook_getRecipesByCategory' for filtered results or 'mcp_howtocook_recommendMeals' for suggestions, leaving the agent to infer usage 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.

Deploy Server

Other Tools

Related Tools