Spaces by Peakflo

workflow_add_node

Adds one step (node) to the open draft of a workflow. Required: workflowId, the node type and its position. The change stays in the draft until a version is saved. It does not run the workflow, start the new step or contact any connected app.

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>",
      "nodeData": "<nodeData>"
    },
    "name": "workflow_add_node"
  }
}

Input Schema

Name	Required	Description
`nodeData`	Yes	JSON string of the node data including type, name, inputs, outputs, parameters, position, etc.
`workflowId`	Yes	The workflow ID
`versionLabel`	No	Optional label for this version (e.g. "Added PDF reader node"). If omitted, defaults to "Version N".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world, but the description adds real context: edits are draft-scoped until a version is saved, nothing executes, and no connected app is contacted. What's missing is the return value (e.g., the new node's id), which matters for a chained add_edge call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero filler, with the core action front-loaded and the persistence constraint and non-effects following in a logical order.

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

Completeness4/5

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

For a 3-parameter draft-mutation tool with full schema coverage and no output schema, the description covers the important behavioral context. The one remaining gap is that it doesn't indicate what the call returns, which the agent needs to chain into edge creation.

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 three parameters are already documented. The description restates that workflowId plus the node's type and position are required, which mirrors the nodeData schema text ('including type, ... position, etc.') rather than adding new meaning. Baseline 3 applies.

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 ('Adds one step (node) to the open draft of a workflow') with scope narrowed to the draft, which cleanly separates it from workflow_update_node, workflow_delete_node and workflow_add_edge.

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

Usage Guidelines4/5

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

Gives clear when/when-not guidance: the edit lands in the draft, requires a version save to persist, and explicitly does not run the workflow or start the step. It stops short of naming the follow-up/alternative tools (workflow_save_version, workflow_add_edge, workflow_update_node) by name.

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

All Spaces by Peakflo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.