Skip to main content
Glama

Get recipe

liftbrain_get_recipe
Read-only

A recipe in full: the ingredients in grams (raw meat, dry rice and pasta) scaled to the servings asked for, the method, kcal and macros per serving and per 100 g of the cooked dish, and the cooked weight.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "liftbrain_get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe recipe's slug, as the recipe search gives it
servingsNoScale to this many servings; the recipe's own when left out

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"From liftbrain_search_recipes"New value: +"The recipe's slug, as the recipe search gives it"
  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 declare this is a safe, non-destructive, closed-world read, so the description only needs to add content-level behavior – and it does, enumerating exactly what comes back (grams, method, kcal/macros per serving and per 100 g, cooked weight). It does not cover failure behavior for an unknown slug, but the read-only nature needs little else.

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?

A single front-loaded sentence that opens with the resource and then enumerates payload contents, with no filler. The parenthetical about raw weights is dense but earns its place; the sentence is long but not padded.

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 simple two-parameter read tool with no output schema, the description carries the payload explanation well and covers scaling behavior. The only real gap is what happens with an invalid or missing slug, which is minor at this complexity level.

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 schema already documents both parameters and a baseline 3 would apply. The description nonetheless adds genuine semantics beyond the schema by clarifying that amounts are raw weights in grams (raw meat, dry rice and pasta) and that values are scaled to the requested servings, including per-serving and per-100 g nutrition.

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 the resource precisely: a full recipe returned with ingredients, method, nutrition and cooked weight. The phrase 'in full' implicitly distinguishes it from the list/search siblings (search_recipes, top_recipes), though it never names them or uses an explicit verb like 'fetch'.

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?

Usage is only implied: 'in full' suggests it is the detail-fetch counterpart to the search tools, and the slug parameter mentions 'as the recipe search gives it', hinting at the search-then-fetch flow. There is no explicit statement of when to use this versus liftbrain_search_recipes or 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.