Skip to main content
Glama

Workflow Graph Tool

workflow_graph

Edit workflow DAG graph structure by adding, updating, or deleting nodes and edges to manage agent execution flows.

Instructions

Edit workflow DAG graph structure. Actions: save_graph (workflow_id, nodes, edges — full graph replace), node_update (workflow_id, node_id, config), node_add (workflow_id, type, config), node_delete (workflow_id, node_id), edge_add (workflow_id, source_id, target_id), edge_delete (workflow_id, edge_id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: save_graph, node_update, node_add, node_delete, edge_add, edge_delete
workflow_idYesThe workflow UUID
nodesYesArray of node objects. Each must have: type (start|end|agent|conditional|human_task|switch|dynamic_fork|do_while), label (string), and optionally agent_id, skill_id, config.
edgesNoArray of edge objects. Each must have: source_node_index (int), target_node_index (int), and optionally condition, label, is_default.
node_idYesThe workflow node UUID
labelNoNew label for this node
agent_idNoUUID of the agent to assign to this node. Pass empty string to detach.
skill_idNoUUID of the skill to assign to this node. Pass empty string to detach.
crew_idNoUUID of the crew to assign to this node. Pass empty string to detach.
configNoNode configuration object (e.g. timeout, retries, prompt_override)
expressionNoCondition expression for conditional/switch nodes (e.g. "output.score > 0.8")
position_xNoHorizontal position on the canvas
position_yNoVertical position on the canvas
typeYesNode type: agent (executes an agent), conditional (branches on expression), human_task (waits for human), switch (multi-way branch), dynamic_fork (parallel split), do_while (loop)
source_node_idYesUUID of the source node (where the edge originates)
target_node_idYesUUID of the target node (where the edge points to)
conditionNoCondition object for conditional edges (e.g. {"field": "score", "op": "gt", "value": 0.8})
case_valueNoCase value for switch node routing — this edge is taken when the expression equals this value
is_defaultNoMark this as the default edge when no other condition matches. Default: false
source_channelNoOutput port of the source node, e.g. "on_success", "on_error", "on_timeout"
target_channelNoInput slot of the target node (for multi-input nodes)
edge_idYesThe workflow edge UUID to delete
Behavior3/5

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

Discloses that save_graph performs a 'full graph replace' (destructive), but with no annotations provided, lacks other critical behavioral details like atomicity, validation rules, or error handling for the mutation operations.

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?

Extremely dense and efficient—every word serves the purpose of documenting the six possible actions and their signatures. Slightly sacrifices readability for density but avoids waste.

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

Completeness3/5

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

Covers the action-to-parameter mapping for 22 parameters, but lacks output schema documentation and behavioral context (validation, side effects) expected for a complex graph manipulation tool with nested object structures.

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?

With 100% schema coverage, the schema documents parameters well. The description adds value by mapping which parameters belong to which action (e.g., 'node_update (workflow_id, node_id, config)'), serving as a quick reference.

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 'Edit workflow DAG graph structure' with specific actions listed. Clear verb and resource, but lacks explicit differentiation from sibling 'workflow_manage' which likely handles metadata vs graph structure.

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

Usage Guidelines2/5

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

Lists available actions but provides no guidance on when to use this tool versus 'workflow_manage' or prerequisites like workflow existence. No 'when-not' or alternative suggestions.

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/escapeboy/agent-fleet-o'

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