Skip to main content
Glama

Meal Planner — free recipe beta

search_public_recipes

Read-onlyIdempotent

Find complete free samples and recent public first-dinner recipes by ingredient/name words or reviewed dietary labels such as vegetarian (also veggie or meat-free). An exact published title is a name lookup and does not establish dietary suitability. Otherwise all diet and ingredient words must match; neutral words such as dinner or with are ignored. max_minutes bounds the published estimate: timing_basis distinguishes total from cooking-only, which excludes prep. Unlabeled weekly recipes are not inferred suitable for a diet. Not personalized or certified allergy-safe. No account required.

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": "search_public_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
max_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description adds genuine context beyond them: 'No account required', not personalized or certified allergy-safe, and that unlabeled weekly recipes are not inferred suitable. It does not, however, explain result set size or pagination behavior.

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 intent is front-loaded with the core verb, but the body is a dense chain of clauses ('Find complete free samples and recent public first-dinner recipes...') that is harder to parse than necessary; several sentences could be tightened without losing meaning.

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?

For a 3-parameter search tool with no output schema and only safety annotations, the description supplies substantial behavioral context (diet matching rules, timing semantics, account/safety caveats). The main gap is the unexplained limit parameter and the orphaned timing_basis reference.

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?

Schema coverage is 0%, so the description must compensate. It explains query matching and that max_minutes 'bounds the published estimate', but leaves the limit parameter completely unexplained and references a 'timing_basis' distinction that does not appear as a schema parameter, creating ambiguity rather than clarity.

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 states a clear verb+resource ('Find ... recipes') and specifies the searchable fields: ingredient/name words and reviewed dietary labels. It is specific about what can be searched and what counts as a match, though it never names its siblings (get_public_recipe, get_meal_planner_info) to differentiate itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real query semantics — all diet/ingredient words must match, neutral words like 'dinner'/'with' are ignored, and an exact title is treated as a name lookup rather than a dietary filter. However, it offers no guidance on when to use this search versus the sibling get_public_recipe for a single lookup, leaving the routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources