spoonacular-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOONACULAR_API_KEY | Yes | Your Spoonacular API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recipesC | Search for recipes based on ingredients, diet, cuisine, and other criteria |
| get_recipe_informationA | Get detailed information about a specific recipe by ID |
| search_ingredientsC | Search for ingredients by name |
| analyze_nutritionC | Analyze nutrition information for a list of ingredients |
| find_recipes_by_ingredientsC | Find recipes that can be made with the ingredients you have |
| get_random_recipesA | Get random recipes, optionally filtered by tags |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes: search_recipes vs find_recipes_by_ingredients could be confused, but descriptions clarify the different focus (general search vs. ingredient-based). Overall, the set is well-disambiguated.
All tool names use snake_case and follow a verb_noun pattern, with slight variation: find_recipes_by_ingredients includes a preposition, and get_recipe_information vs get_random_recipes differ slightly in structure. Minor inconsistencies, but overall consistent.
6 tools cover the core functionalities of a recipe service: searching, getting details, ingredient lookup, nutrition analysis, and random recipes. The count is well-scoped without being too few or too many.
The tool set covers essential operations for a recipe discovery and analysis service: search by various criteria, get detailed info, ingredient search, nutrition analysis, and random selection. There are no obvious gaps for its intended domain.