Skip to main content
Glama

execute_flow

Run conditional, iterative, or error-handling flows (if/for/try) within a robot session to control automation execution.

Instructions

Execute structured flow (if/for/try) within a session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoItems to iterate when structure="for".
rethrowNoWhether to rethrow after except/finally.
item_varNoVariable name to bind each item in for-each loops.item
conditionNoExpression for if/conditional flows.
structureYesFlow type ("if", "for", "try").
try_stepsNoSteps for the try block (when structure="try").
else_stepsNoSteps for the else branch (if).
session_idYesSession id to run the flow in.
then_stepsNoSteps for the main branch (if/loop body/try block).
except_stepsNoSteps for the except block.
finally_stepsNoSteps for the finally block.
max_iterationsNoMaximum iterations for for-each loops.
except_patternsNoError patterns to match for except handling.
stop_on_failureNoWhether to stop loop/branch execution on first failure.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Execute structured flow' with no disclosure of behavioral traits such as side effects, error handling, authentication needs, or rate limits. The description is minimal.

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?

The description is a single sentence that front-loads the core purpose. It is concise but could benefit from additional context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool (14 parameters, control flow structures), the description is incomplete. It lacks information about how flows execute, output schema details, and important constraints. The description does not adequately prepare an agent for correct use.

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 all 14 parameters have descriptions in the schema. The tool description adds no additional meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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 clearly states the tool 'execute' 'structured flow' and specifies the flow types (if/for/try) within a session. This distinguishes it from siblings like 'execute_step' which likely executes a single step, and 'execute_batch' which runs a batch.

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 usage when needing to run control flow logic, but does not provide explicit guidance on when to use this tool versus alternatives like 'execute_step' or 'execute_batch'. No exclusions or comparisons are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/manykarim/rf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server