bridgecore

Plan an automation (tool per step)

plan_automation

Read-only

Turn a plain-words need into steps (one trigger + actions) and pick the concrete tool for each step from 3,000+ app capabilities (n8n nodes, OpenAPI, MCP). Reports a gap when the named app cannot do a step instead of substituting another app.

Input Schema

Name	Required	Description	Default
`need`	Yes	What should happen, in plain words: 'when <trigger> <action>, then <action>'.
`alternatives`	No	Runner-up tools to list per step (1-5).

Output Schema

Name	Required	Description	Default
`need`	Yes
`steps`	No	trigger + actions, each with the best tool, alternatives, or a gap

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedOutput schema / properties / 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)."

Changed1 schema field changedOct 15, 2026

changedOutput schema / properties / 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)."

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / alternatives / description
```
Added value: +"Runner-up tools to list per step (1-5)."
```

addedInput schema / properties / need / description

Added value: +"What should happen, in plain words: 'when <trigger> <action>, then <action>'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "need": {
+      "type": "string"
+    },
+    "steps": {
+      "description": "trigger + actions, each with the best tool, alternatives, or a gap",
+      "items": {
+        "additionalProperties": true,
+        "description": "One step: text, kind (trigger/action), the chosen tool or a gap.",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "need"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds genuinely useful behavior beyond that: it searches 3,000+ capabilities (n8n nodes, OpenAPI, MCP) and, distinctively, reports a gap rather than silently substituting a different app. That no-substitution policy is exactly the kind of behavioral trait an agent needs. It stops short of describing plan shape or failure modes.

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

Conciseness5/5

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

Two sentences, no filler, and the core action plus the gap-reporting guarantee are front-loaded. Every clause carries information about scope or behavior.

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 an output schema present and annotations covering the safety profile, the description only needs to supply scope and behavior, which it does. The remaining gap is pipeline positioning: nothing tells the agent how this relates to do or make_n8n_workflow, which matters for a planning tool in a multi-step toolset.

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 description coverage is 100%, so both parameters (need, alternatives) are already fully documented, including the trigger/action phrasing and the 1-5 range. The description adds no syntax or meaning beyond the schema, which is the expected baseline here.

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: converts a plain-words need into a trigger+actions plan and selects a concrete tool per step from a large capability catalog. The scope is clear and clearly read-oriented, but it never names the siblings (do, make_n8n_workflow, find_recipe) that an agent would weigh it against.

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 tool is framed as the planning stage that precedes execution, so an agent can infer it should be called before 'do' or 'make_n8n_workflow'. There is no explicit when-to-use, when-not, or naming of alternatives, and no stated prerequisite tying it to the sibling tools.

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

All bridgecore tools Inspect

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

Need Help?