Skip to main content
Glama

Search recipes

liftbrain_search_recipes
Read-only

Searches LiftBrain's high-protein recipes. Each result has kcal, protein, fat and carbs per serving, the time and the page. Filter by words (dish or ingredient, in English), a tag, the most kcal or the least protein per serving; with no filters it lists them all.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly recipes with this tag
queryNoEnglish words, e.g. "chicken rice" or "oats"
maxKcalNoMost kcal per serving
minProteinGNoLeast protein per serving, in grams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag / description
      Added value: +"Only recipes with this tag"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's added value is the result shape: kcal, protein, fat, carbs per serving, time and page. It does not mention pagination limits or maximum result counts, which is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and the result contract before the filter mechanics. The second sentence is dense but every clause (words, tag, kcal, protein, no-filter default) carries information.

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?

With no output schema, the description compensates by naming the returned fields, and all four optional parameters are covered by both schema and prose. Only retrieval limits and ordering behavior for multi-result queries are left unstated.

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 coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: the query matches dish or ingredient and must be English, and the default with no filters is to list everything. That clarifies how the filters compose and what happens when none are supplied.

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?

States a specific verb and resource ("Searches LiftBrain's high-protein recipes") and enumerates the returned fields, so the agent knows exactly what comes back. It does not explicitly name how it differs from liftbrain_top_recipes or liftbrain_get_recipe, though "with no filters it lists them all" hints at the broad-list behavior.

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?

Implies usage through the filter list and the no-filter default, giving the agent a sense of when the tool is a plain listing versus a filtered search. There is no explicit when-not guidance and no named alternative despite closely related siblings like liftbrain_top_recipes.

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.