Skip to main content
Glama

Export Diagram as Graph

flowzap_export_graph
Read-onlyIdempotent

Parse FlowZap Code into a structured JSON graph (lanes, nodes, edges).

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

Input Schema

NameRequiredDescriptionDefault
codeYesFlowZap Code to parse

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered structurally. The description adds useful return-shape context (lanes, nodes, edges) but says nothing about behavior on malformed code, no error semantics, and no mention that this is a pure transformation with no side effects beyond what annotations imply.

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?

One sentence, front-loaded with the verb and the output shape, with zero filler. It is arguably too terse rather than too long, but nothing is wasted.

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?

With one well-documented parameter, full annotation coverage, and no output schema, the description supplies the one thing structure cannot: what the returned graph contains (lanes, nodes, edges). Missing pieces (error behavior, sibling routing) are moderate but not blocking for correct invocation.

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% and the single required parameter carries its own description ("FlowZap Code to parse"), so the schema does the heavy lifting. The description only echoes the parameter meaning and gives no indication of expected syntax, size limits, or a pointer to flowzap_get_syntax for format guidance.

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 ("Parse") and resource ("FlowZap Code") plus the output shape ("structured JSON graph (lanes, nodes, edges)"), which is clearer than a bare restatement. It does not, however, distinguish itself from near-siblings like flowzap_validate, flowzap_diff, or flowzap_artifact_to_diagram, so an agent must infer the boundary.

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?

No when-to-use guidance at all: nothing says whether this is a pre-step before flowzap_diff/flowzap_validate, or how it differs from flowzap_artifact_to_diagram which also produces diagrams. The only implicit cue is that it takes FlowZap Code rather than an artifact.

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.