Flowra

Get tool schemas

FLOWRA_GET_TOOL_SCHEMAS

Read-onlyIdempotent

Load the input schema and tool type for exact tool slugs, so you can build correct arguments before running them with FLOWRA_MULTI_EXECUTE_TOOL. These slugs are NOT bound functions — never emit them as a tool_call name. Call FLOWRA_DISCOVER_TOOLS first if you do not have the slug. Set includeOutputSchema=true only when you need a trigger or webhook payload shape. Pass session.id from DISCOVER to stay in the same session.

Workflow action nodes flatten tool data into the node state: after an action node "fetch", use fetch.content / fetch.title in prompts and inputMapping — not fetch.data.content. GET_TOOL_SCHEMAS may show an envelope with properties.data; CREATE_OR_UPDATE_WORKFLOW validation uses the flattened field names only.

Input Schema

Name	Required	Description
`session`	No	Optional meta session.id from DISCOVER
`toolSlugs`	Yes	Exact slugs from Known tools, pins, or DISCOVER — never invent
`includeOutputSchema`	Yes	Include outputSchema (trigger payloads). Default false

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error if any occurred during the execution of the action
`message`	No
`successful`	No	Whether or not the action execution was successful or not

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "properties": {
+        "executionHint": {
+          "description": "How to run these slugs — they are not bound functions"
+        },
+        "notFound": {
+          "description": "Slugs not found",
+          "items": {}
+        },
+        "session": {
+          "description": "Echoed session — never minted here",
+          "properties": {
+            "id": {
+              "description": "Meta session id (empty if none)"
+            },
+            "instructions": {
+              "description": "How to reuse session.id"
+            }
+          }
+        },
+        "success": {
+          "description": "True when every requested slug was found"
+        },
+        "toolSchemas": {
+          "description": "Definitions keyed by toolSlug",
+          "propertyNames": {}
+        }
+      }
+    },
+    "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"
+}

First observedSep 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further: slugs are NOT bound functions and must never be emitted as a tool_call name, and it discloses the workflow action node behavior where `data` is flattened into node state (fetch.content vs fetch.data.content). That is non-obvious behavioral context an agent could not get from structured fields.

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 core purpose, prerequisite, and the critical 'not a tool_call name' warning. The second paragraph about workflow flattening is dense but relevant, though it drifts toward workflow-authoring guidance rather than this tool's own invocation and could be tightened.

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?

An output schema exists so return values need no explanation, yet the description still clarifies the envelope-vs-flattened distinction that directly affects how the output is consumed and validated by CREATE_OR_UPDATE_WORKFLOW. Nothing needed to call it correctly 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 real meaning beyond the schema descriptions: session.id is tied to DISCOVER for session continuity, and includeOutputSchema is scoped to trigger/webhook payload shapes rather than a generic boolean.

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?

States a specific verb and resource — load input schema and tool type for exact slugs — and names the downstream consumer (FLOWRA_MULTI_EXECUTE_TOOL). It also explicitly distinguishes itself from the discovery sibling by requiring slugs rather than producing them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use rules: call FLOWRA_DISCOVER_TOOLS first if the slug is unknown, set includeOutputSchema=true only when a trigger or webhook payload shape is needed, and pass session.id from DISCOVER to stay in the same session. Alternatives and conditions are spelled out rather than implied.

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

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