MIT
Recipes Daily
Server Details
Search recipes-daily.com by dish, ingredient, cuisine, method, meal or occasion.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly defined and distinct by virtue of being the only option.
Naming Consistency5/5
The singular tool name 'search_recipes' follows a consistent verb_noun pattern, which is clear and predictable. Even with only one tool, the naming convention is internally consistent.
Tool Count2/5
The server has only one tool, which feels too thin for a recipe-focused server. While search is a core function, a typical recipe service would benefit from additional tools like get_recipe_details or browse_by_category, making this count inadequate for the apparent scope.
Completeness2/5
The search tool provides a shortlist with limited fields, but there is no way to retrieve full recipe details or perform other common operations (e.g., browse categories, get a specific recipe by ID). This leaves significant gaps for agents that need richer recipe data.
Available Tools
1 toolsearch_recipesSearch recipesARead-onlyIdempotentInspect
Search the recipes published at recipes-daily.com by dish, ingredient, cuisine, method, meal or occasion. Returns a shortlist — title, absolute URL, description, total time, servings and categories — so candidates can be ruled out without opening them.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based. The response names the next page when there is one. | |
| limit | No | Results per page. | |
| query | No | What to search for. Titles and descriptions are indexed, so a word or short phrase matches better than a full question, and there are no boolean operators. Omit it to list every recipe, newest first. |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so the description doesn't need to repeat that. It adds useful behavioral context: the search indexes titles and descriptions, omitting query lists all recipes newest first, and the response includes pagination info (next page). This goes beyond the schema.
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 two sentences, front-loaded with the core purpose, and every clause adds value. It efficiently conveys the search scope, return format, and usage nuance without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (3 optional params, no output schema), the description covers the essential aspects: what it searches, what it returns, and key query behaviors. It doesn't detail the exact response structure, but the description of the shortlist fields is sufficient for an agent to understand the output. No output schema exists, so the description partially compensates.
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?
Schema description coverage is 100%, so the schema already documents all parameters well. The description adds value by explaining query behavior (matching strategy, no boolean operators, omission behavior) and pagination context (response names next page). This complements the schema without redundancy.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches recipes published at a specific site by multiple criteria (dish, ingredient, cuisine, method, meal, occasion). It distinguishes itself by specifying the return format (shortlist with title, URL, description, etc.) and the purpose of ruling out candidates without opening them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool (to search recipes and get a shortlist for filtering) and provides guidance on query formulation (word or short phrase matches better than full question, no boolean operators). It doesn't explicitly mention alternatives, but since there are no sibling tools, this is acceptable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityDmaintenanceSearch 14,000+ x402-enabled HTTP APIs by keyword. Agents pay $0.01 USDC per search via x402 micropayments on Base mainnet — no API keys or accounts required.1502MIT
- Alicense-qualityDmaintenanceUse Tavily Search to search for news pages or images.MIT
- AlicenseAqualityDmaintenanceEnables searching the NIAID Data Ecosystem for biomedical research resources including datasets, clinical studies, and publications using Elasticsearch queries.3MIT