Skip to main content
Glama

edit_flow

Edit canvas wiring, entity lifecycle (create_entity, edit_entity), block positions, flow block order, or quota ordering/matrix generation. To remove a flow entity, use delete_flow_entity instead.

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": {
      "survey_id": "<survey_id>"
    },
    "name": "edit_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYesSurvey UUID
edit_entityNoEdit a flow entity with a typed patch. Runs on its own: other patches in the same call are ignored, and create_entity takes precedence over it.
snap_canvasNoAuto-arrange the Flow canvas
create_entityNoCreate a condition set, variable, quota, permutation set, logic branch, or quota status link. Runs on its own: any other patch in the same call is ignored.
block_positionNoMove one block on the Flow canvas. Layout only; the respondent path does not change, and auto-arrange is marked as overridden.
connect_blocksNoDraw (or replace) the single outgoing connector of a block on the Flow canvas; this replaces a branch connector on that block too.
reorder_quotasNoReorder the survey's quotas.
flow_block_orderNoReplace the survey's Flow with a plain sequence of these blocks and renumber them to match, dropping any branches, randomizers, or other Flow elements between blocks.
branch_arm_targetNoPoint one arm of a Logic Split branch at a block.
generate_quota_matrixNoCreate a crossed grid of quotas, one per combination of the dimensions' values, in a new quota group. The generated quotas are added after any existing ones.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the agent knows this mutates. The description adds nothing about the interaction between the sub-patches (that one patch suppresses the others, and create_entity wins over edit_entity, lives only in schema text) nor about the fact that flow_block_order discards branches and randomizers. Credit for the delete routing note, but key behavioral caveats stay buried in schema.

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?

Two sentences, front-loaded with the operation inventory and closing with the routing exclusion. The enumeration is long but each item is a distinct capability an agent must know exists, so little is wasted. A short note on mutual exclusivity would have been worth more than some of the listing.

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?

With 10 parameters, nested objects, and a true output schema, this is a high-complexity dispatcher, and the description is a bare capability inventory. The critical calling constraints (patches are mutually exclusive, create_entity takes precedence, required confirm flags, entity IDs come from read_flow) appear only in nested schema descriptions, so the top-level definition under-serves the tool's complexity.

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 coverage is 100%, so baseline is 3. The description adds a coarse map from operation names to parameter groups (canvas wiring, block positions, quota ordering), which helps an agent pick the right patch, but it adds no syntax, constraints, or format detail beyond the schema.

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?

The description names a specific verb (Edit) and enumerates the resources touched: canvas wiring, entity lifecycle via create_entity/edit_entity, block positions, flow block order, and quota ordering/matrix generation. It also distinguishes itself from delete_flow_entity explicitly. It is a union tool without a single crisp scope, 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 Guidelines3/5

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

Only one routing rule is given: use delete_flow_entity to remove a flow entity. There is no guidance on when to pick this versus edit_block for blocks, or that read_flow/read_block should be called first to obtain the UUIDs the sub-operations require. Usage context is implied by the operation list rather than stated.

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