Skip to main content
Glama

Get a recipe

get_recipe
Read-onlyIdempotent

One recipe in full: what it does, the Actor and input it sends, schedule, de-duplication, setup steps, known limits and, with include_workflow=true, the importable n8n workflow JSON (built-in nodes only).

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

Input Schema

NameRequiredDescriptionDefault
slugYesRecipe slug from find_recipe, or the recipe page URL.
include_workflowNoInclude the n8n workflow JSON (several KB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 a safe, idempotent, closed-world read. The description adds real behavioral context beyond them: the exact payload sections returned (Actor, input, schedule, de-duplication, setup steps, known limits) and that include_workflow returns a multi-KB importable n8n workflow restricted to built-in nodes. It does not cover not-found or invalid-slug behavior.

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 leads with scope and then enumerates contents, with no filler. The long enumerated clause is dense but every item describes the returned payload, so little is wasted.

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 carries the burden of describing the return value and does so thoroughly, including the conditional workflow payload. Minor gaps remain around failure cases and slug normalization, but an agent has enough to call it correctly.

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 baseline is 3. The description still contributes meaning: include_workflow yields importable workflow JSON and the JSON is limited to built-in nodes only, a constraint absent from the schema. The slug's dual form (slug or page URL) is left to the schema.

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?

"One recipe in full" names the verb (retrieve) and resource (a single recipe), and the enumerated contents make it distinguishable from find_recipe, which implies lookup. It never explicitly contrasts with find_recipe, but the singular-scope framing does the work.

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: the slug is said to come from find_recipe, which suggests this is the detail-fetch step after a search. There is no explicit when-to-use/when-not statement and no guidance on when the workflow JSON is unnecessary.

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