Skip to main content
Glama

Open flow editor

open_flow_editor
Read-only

Used by the Wavelength flow viewer only. Returns a one-time link that opens the full Wavelength editor for a flow inside the chat.

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": {
      "flow_id": "<flow_id>"
    },
    "name": "open_flow_editor"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesThe flow id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and notably idempotentHint=false; the description's "one-time link" explains why non-idempotency holds and describes the return artifact (a chat-scoped editor URL), which is real added value given there is no output schema. It stops short of stating link expiry, single-use enforcement, or whether calling it grants any access, so the disclosure is useful but incomplete.

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?

Two short sentences, zero filler, with the audience restriction placed first so an agent can bail out immediately before reading the mechanics.

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 one-parameter, no-output-schema tool this covers the essentials: who it is for, what it produces, and where the link applies. Missing only operational detail such as link lifetime or re-issuance behavior, which are minor for a read-only convenience tool.

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?

There is a single parameter and schema coverage is 100%, so the schema already documents flow_id fully. The description adds nothing about the id's form or where to obtain it (e.g., from get_flow or a prior list call), which is exactly the baseline-3 case.

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?

Names a specific effect (returns a one-time link that opens the full Wavelength editor for a flow) rather than restating the title. It also scopes the tool to a particular consumer (the flow viewer), which separates it from the general edit_flow / show_flow family, though it never names those siblings directly.

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?

"Used by the Wavelength flow viewer only" functions as an explicit when-not: an agent that is not the flow viewer knows to avoid this tool and reach for edit_flow instead. There is no positive statement of the caller-side condition under which it should be used, and no alternative is named, which keeps it below a 5.

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