Skip to main content
Glama

Patch an Existing Diagram

flowzap_apply_change
Destructive

Apply structured patch operations (insert/remove/update nodes or edges) to FlowZap Code. Returns an advisory quality block listing process defects (e.g. a step with no incoming edge, more than one start circle); the diagram is still created — fix the code and call again.

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": {
      "code": "<code>",
      "operations": "<operations>"
    },
    "name": "flowzap_apply_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCurrent FlowZap Code
operationsYesArray of patch operations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false and readOnly=false, so mutation semantics are covered; the description adds genuinely new behavior — that quality defects are reported in an advisory block and do NOT block the operation ('the diagram is still created'). That non-blocking validation loop is the key behavioral trait an agent needs. It stops short of saying what state is replaced or lost when a patch is destructive.

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 tight sentences with the action front-loaded and the return-behavior caveat second; nothing is filler. The phrase 'the diagram is still created' is imprecise for a patch operation and slightly muddies the otherwise crisp wording.

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 no output schema, the description carries the burden of explaining returns and does so adequately for the quality block. But for a destructive two-parameter mutation tool it omits the operation payload contract and never points to flowzap_get_syntax or flowzap_validate for the FlowZap Code format, leaving a real gap for first-time callers.

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 the baseline is 3, and the description does add meaning by naming the permitted operation types. However, the actual shape of each operation object is undocumented in both the schema ('Array of patch operations', items typed as a bare object) and the description, leaving the critical payload format to guesswork.

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 gives a specific verb+resource pair ('Apply structured patch operations ... to FlowZap Code') and enumerates the operation kinds (insert/remove/update nodes or edges), so the agent knows exactly what class of action this performs. It never names or contrasts with any sibling (flowzap_fix, flowzap_validate, flowzap_diff), so differentiation is left to inference.

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 only situational guidance is post-invocation ('fix the code and call again' when defects are reported); there is no statement of when to choose this over flowzap_fix, flowzap_validate, or flowzap_diff, nor any prerequisite about the code already existing. An agent must infer the routing from sibling names alone.

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.