Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

createWorkflowEdge

Connects two workflow nodes with an edge, optionally applying a condition, to define execution paths in a staged workflow.

Instructions

Connect two nodes with an edge

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflowId": "<workflowId>",
      "sourceNodeId": "<sourceNodeId>",
      "targetNodeId": "<targetNodeId>"
    },
    "name": "createWorkflowEdge"
  }
}

Input Schema

NameRequiredDescriptionDefault
conditionNoOptional edge condition
workflowIdYes
sourceNodeIdYes
targetNodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether this is a mutation, whether duplicate edges are rejected, what permissions are required, or what happens when the condition is not met. For a write operation with zero annotation coverage, this is a significant gap.

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 single sentence is front-loaded and free of unnecessary wording. It is efficient, though its brevity contributes to the specification gaps captured in other dimensions.

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?

This is a mutation tool with four parameters, a nested condition object, no annotations, and no output schema, yet the description is one short sentence. Critical details about required permissions, edge uniqueness, condition evaluation, and return behavior are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, with just the condition parameter documented as "Optional edge condition." The description says "connect two nodes," which loosely implies sourceNodeId and targetNodeId, but it does not explain workflowId's scoping role or the expected format of the nested condition object. The description does not compensate for the low schema coverage.

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?

"Connect two nodes with an edge" states a specific verb (connect) and resource (nodes/edge), which is clear enough for an agent to understand the operation. However, it does not distinguish this from sibling tools like createWorkflowNode or createWorkflow, so it falls short of a 5.

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?

The description provides no when-to-use guidance, no prerequisites, and no alternatives. It does not explain when to create an edge versus a node, or whether nodes must already exist before connecting them.

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