Skip to main content
Glama

Find my recipes

search_recipes
Read-onlyIdempotent

Search the user's own recipes and those shared with them, by text, category, filing facet, ingredient or status. Read-only. All filters are optional and combine with AND. Paged: returns {count, offset, recipes:[{id, title, filed, categories, servings, shared_by}], has_more, next_offset}. Use get_recipe to open one.

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_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOne free tag
dietNoe.g. "Vegan"
limitNoPage size, 1-1000, default 20
queryNoFree text, case/accent-insensitive partial match on title, description, filing and categories
quickNoOnly quick recipes (short total time)
courseNoCourse facet, e.g. "dessert"
hiddenNoList shared recipes the user hid instead
methodNoe.g. "Grill"
offsetNoResults to skip, default 0; use next_offset
statusNoOnly drafts or only saved recipes
cuisineNoe.g. "Italian"
categoryNoCategory path, includes subcategories, e.g. "Desserts > Pies"
occasionNoe.g. "Weeknight"
ingredientNoIngredient name contained, e.g. "chicken"
shared_with_meNoOnly recipes others shared with the user
main_ingredientNoMain-ingredient facet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), but the description still adds real value: the AND-combination rule across filters, the paged nature, and the exact envelope returned. Return-shape disclosure matters here since no output schema exists. It stops short of stating default page size or result-count limits, which the schema carries separately.

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?

Three tightly packed sentences: scope first, behavioral rule second, return contract third, next-step pointer last. No filler, no restatement of the tool name, and the pagination envelope is written inline rather than described vaguely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters, zero required, and no output schema, the description supplies exactly the two things the structured data cannot: how filters interact, and what the response looks like including has_more/next_offset. An agent has everything needed to call this correctly and to page through results.

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 description coverage is 100%, so every one of the 16 parameters is already documented individually; the description can only add cross-parameter semantics. It does contribute the AND-combination rule, which is not in the schema, but otherwise just summarizes the same facets the schema already names. Baseline 3 applies.

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?

States a specific verb and resource (search) plus the exact corpus covered — the user's own recipes and those shared with them — and enumerates the axes of search (text, category, filing facet, ingredient, status). This is clearly distinguishable from siblings like get_recipe, list_history, or suggest_dishes.

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?

Explicitly routes to get_recipe for opening a single result, and clarifies that all filters are optional and combined with AND, which is the main ambiguity an agent would hit with 16 optional params. It does not name a when-not-to-use case (e.g. browsing vs. targeted lookup) or clarify when to prefer ingredient vs. query, so it falls short of a 5.

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