Skip to main content
Glama

Find an automation recipe

find_recipe
Read-onlyIdempotent

Find step-by-step n8n recipes that move live web data into a destination (Google Sheets, Slack, Notion, HubSpot, email, Discord, webhook, Qdrant) for a task such as 'new Zillow listings to Slack', plus matching use cases and agent skills. Suggests Actors when no recipe fits.

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": {
      "task": "<task>"
    },
    "name": "find_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat should happen, e.g. 'daily Google Maps leads into a spreadsheet'.
limitNo
destinationNoOptional: where the data should go (Google Sheets, Slack, Notion, HubSpot, Email, Discord, Webhook, Qdrant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results include use cases and agent skills and that Actors may be suggested as a fallback, but says nothing about result volume, ranking, or empty-result behavior beyond the fallback hint.

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 verb and resource, followed by the destination list and the fallback note. The parenthetical destination list is long but earns its place by signaling accepted values.

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?

For a read-only, three-parameter discovery tool with no output schema, the description covers what it returns (recipes, use cases, agent skills), what inputs mean, and what happens when nothing matches. Nothing essential to calling it correctly is missing.

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 67%, so task and destination are already documented in the schema with examples. The description reinforces the task/destination pattern through its example phrasing but adds no new constraints on limit or on how destination values are matched.

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?

The description states a specific verb and resource ("Find step-by-step n8n recipes") and scopes it to moving live web data into named destinations, with a concrete example. It distinguishes itself from get_recipe by implying discovery rather than fetching a specific known recipe.

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?

It clearly says the tool is for task-shaped discovery and that it also returns matching use cases and agent skills, and it names the fallback behavior (suggesting Actors when no recipe fits). It does not explicitly contrast with get_recipe or search_tools, so an agent must infer that get_recipe is for retrieving a known recipe.

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