Skip to main content
Glama
Sign In

bridgecore

by io.github.chinlee2200-dotcom
OverviewDiscussionsAdmin

Find a ready-made automation recipe

find_recipe
Read-only

Find a ready-made automation recipe for a plain-words need, e.g. 'when a typeform is submitted add a row to google sheets and send a slack message'. Returns the best matching recipes (apps chained with →, what it does, the n8n workflow JSON, the blanks to fill and accounts to connect) plus matching public n8n templates (title + official link). Covers connecting apps, automating a workflow, syncing tools, and getting notified when something happens.

Input Schema

NameRequiredDescriptionDefault
needYesWhat should happen, in plain words. Start with 'when …' for the trigger.
limitNoHow many recipes to return (1-10).

Output Schema

NameRequiredDescriptionDefault
needYes
recipesNomatching tested recipes, each with its n8n workflow, blanks and accounts
planned_stepsNo
public_templatesNopublic n8n templates: title + official link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / planned_steps / items / description
      Previous value: -"One step: text, kind (trigger/action), the chosen tool or a gap; irreversible (sends/posts/deletes/pays) and approval_gate (an Approve/Decline message runs first)."New value: +"One step: text, kind (trigger/action), the chosen tool or a gap; reversibility = read-only (changes nothing) / reversible (undo by hand) / irreversible (sends, posts, deletes, pays — out in the world), and approval_gate (an Approve/Decline message runs first)."
  2. Changed1 schema field changed
    • changedOutput schema / properties / planned_steps / items / description
      Previous value: -"One step: text, kind (trigger/action), the chosen tool or a gap."New value: +"One step: text, kind (trigger/action), the chosen tool or a gap; irreversible (sends/posts/deletes/pays) and approval_gate (an Approve/Decline message runs first)."
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many recipes to return (1-10)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "need": {
+      "type": "string"
+    },
+    "planned_steps": {
+      "items": {
+        "additionalProperties": true,
+        "description": "One step: text, kind (trigger/action), the chosen tool or a gap.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "public_templates": {
+      "description": "public n8n templates: title + official link",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "recipes": {
+      "description": "matching tested recipes, each with its n8n workflow, blanks and accounts",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "need"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes further and discloses the shape of the result (apps chained with →, what it does, the n8n workflow JSON, the blanks to fill, accounts to connect) plus supplementary public templates. No auth, rate-limit, or failure behavior is mentioned, and nothing contradicts the annotations.

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?

Front-loaded with the purpose sentence and the example, followed by return contents and coverage. Slightly long in the final 'Covers connecting apps…' clause, which lists near-synonyms, but overall it earns its space.

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?

Inputs, expected result contents, and scope are all covered, and an output schema exists so return-value detail is not strictly required. An agent has enough to invoke it correctly; only explicit sibling routing is missing.

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 meaning by giving a full example need ("when a typeform is submitted add a row to google sheets…") and framing the input as plain words. That complements the schema's 'start with when…' hint without repeating it verbatim.

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+resource ("Find a ready-made automation recipe") and reinforces it with a concrete plain-words example, so the agent knows exactly what comes back. It does not explicitly distinguish itself from siblings like plan_automation or make_n8n_workflow, though "ready-made" implicitly separates it from workflow-building tools.

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?

The description implies when to use it (turning a plain-words need into a prebuilt recipe) and lists coverage areas such as connecting apps and getting notified. It never names an alternative tool or a condition under which a sibling is the better choice, so routing guidance is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All bridgecore toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources