Skip to main content
Glama

Flowra

by dev.flowra.mcp
OverviewDiscussionsAdmin

Run app tools

FLOWRA_MULTI_EXECUTE_TOOL
Destructive

Run up to 50 action tools in parallel and return every result inline. Only type="action" tools — triggers and webhooks cannot be executed here.

This is how you run any tool that is not already bound as a direct function. Get the exact slug from FLOWRA_DISCOVER_TOOLS or a Known tools list, load its input schema with FLOWRA_GET_TOOL_SCHEMAS (or set includeInputSchemas on DISCOVER and reuse those), and call FLOWRA_MANAGE_CONNECTIONS first if the toolkit has no active connection. Never invent a slug or an argument. Never emit an unbound slug as a tool_call name — only this function runs those slugs, via tools[].toolSlug.

tools must be a non-empty array of { toolSlug, arguments }. Never pass tools: [] or omit tools. If you only have a JSON string, parse it into that array first.

Batch only independent calls; keep a dependent step in a later call so you can read the previous result first. When a result implies more pages, keep going until you have everything.

Never wrap a tool that waits for the user (for example a choice prompt) here. If one is bound, call it directly and wait.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolsYesAction tools to run in parallel (max 50). Not triggers. Must contain at least one { toolSlug, arguments } — never [].
memoryNoDurable facts worth reusing later, as {app: ["fact"]} — ids and mappings, not "sent/fetched" logs. Pass {} when there are none.
sessionNoMeta session.id from DISCOVER (workbench correlation; auth is user-scoped)
thoughtNoOne-sentence rationale
syncResponseToWorkbenchYesStore a workbench snapshot for REMOTE_BASH / JS_REMOTE_WORKBENCH (results still return inline). Needs session.id. Only set true when a sandbox tool is available and the output is large or worth scripting over.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
errorNoError if any occurred during the execution of the action
messageNo
successfulNoWhether or not the action execution was successful or not

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "properties": {
+        "errorCount": {
+          "description": "Failures"
+        },
+        "results": {
+          "description": "Results in input order",
+          "items": {
+            "properties": {
+              "error": {
+                "anyOf": [
+                  {},
+                  {}
+                ],
+                "description": "Error message when failed"
+              },
+              "index": {
+                "description": "Index in the request tools array"
+              },
+              "response": {
+                "anyOf": [
+                  {
+                    "propertyNames": {}
+                  },
+                  {}
+                ],
+                "description": "Payload { data, error, logId, successful } on success and failure"
+              },
+              "success": {
+                "description": "Whether execution succeeded"
+              },
+              "toolSlug": {
+                "description": "Executed tool slug"
+              }
+            }
+          }
+        },
+        "successCount": {
+          "description": "Successes"
+        },
+        "totalCount": {
+          "description": "Tools executed"
+        },
+        "workbenchArtifactId": {
+          "description": "Snapshot id when syncResponseToWorkbench; pass to REMOTE_BASH or omit for latest"
+        }
+      }
+    },
+    "error": {
+      "anyOf": [
+        {},
+        {}
+      ],
+      "description": "Error if any occurred during the execution of the action"
+    },
+    "message": {},
+    "successful": {
+      "description": "Whether or not the action execution was successful or not"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

Score is being calculated.

All Flowra 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