Skip to main content
Glama

Create flow from text

create_flow_from_text

Turn a transcript, call notes, or a spoken description of a process into a saved Wavelength flow. Nodes are auto-laid out. Returns the new flow id, title, node and edge counts, a short list of node labels, and a link to open it.

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": {
      "text": "<text>"
    },
    "name": "create_flow_from_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesA transcript, call notes, or a spoken description of the process to diagram.
titleNoOptional title for the flow. If omitted, the first line of the text is used.
detailNoOptional. high: a high level flow of 6 to 10 steps. detailed: every exception path and rework loop.
org_idNoOptional organization id (from list_organizations). The flow is saved in that organization, where every member can open it.
team_idNoOptional team id to assign the flow to.
directionNoOptional layout direction. vertical stacks ranks top-down (default); horizontal advances left-to-right.
folder_idNoOptional folder id to create the flow in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Optional. high: a high level flow of 6 to 10 steps. detailed: every exception path and rework loop.",
      +  "enum": [
      +    "high",
      +    "detailed"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds two genuinely useful traits beyond that: layout is automatic, and the response includes flow id, title, node/edge counts, sample node labels, and an open link. It still omits cost/latency (this appears to be a generative call), failure behavior on thin or noisy text, and whether repeated identical calls create duplicates despite idempotentHint=false.

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, front-loaded with the core transformation, then a behavioral note about auto-layout, then the return payload. Nothing is repeated and no sentence is filler, especially given the return-value list substitutes for a missing output schema.

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 7-parameter creation tool with a fully documented schema but no output schema, the description covers the important gaps: what the artifact is, that it is persisted, and what comes back. Minor incompleteness remains around generative latency/cost and behavior when the supplied text is unusable.

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 the schema already explains text, title defaults, the high/detailed detail enum, org_id, team_id, direction, and folder_id. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 a specific verb and resource: turning a transcript, call notes, or spoken process description into a saved Wavelength flow. The input types make the scope concrete, but it never distinguishes itself from closely named siblings such as create_flow_from_graph or notes_to_flow, so an agent cannot rule those out from this text alone.

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?

Usage is implied by the accepted inputs (raw natural-language process text rather than a structured graph), which suggests when this tool fits. However, there is no explicit when-not-to-use statement and no named alternative for structured input or for note-taking sources, leaving the routing decision to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources