Skip to main content
Glama

Convert Logs or Specs to Diagram

flowzap_artifact_to_diagram

Convert HTTP logs, OpenAPI specs, or code snippets into a FlowZap diagram.

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": {
      "artifactType": "<artifactType>",
      "content": "<content>"
    },
    "name": "flowzap_artifact_to_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoPreferred view mode
contentYesRaw artifact content
artifactTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety and repeatability profile is covered. The description adds nothing about what actually happens: whether a diagram is persisted or merely returned, whether prior diagrams are affected, or what a caller gets back. With no output schema, this is a meaningful gap.

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?

A single front-loaded sentence with no filler, which is efficient. It is arguably over-compressed given the missing behavioral detail, but as a conciseness measure it is strong.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-read-only conversion tool with three parameters and no output schema, the description leaves too much unstated: the resulting diagram's format, whether it is stored, and how view selection affects output. The annotations cover safety but not the operational semantics an agent needs.

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 67%; required artifactType has no schema description, and the description's enumeration of log/spec/code inputs loosely maps to those enum values. The view parameter is only described in the schema as 'Preferred view mode', and the description never explains the workflow/sequence/architecture choices, so semantics remain thin.

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 states a specific verb (Convert) and resource (a FlowZap diagram), and enumerates the accepted input kinds (HTTP logs, OpenAPI specs, code snippets), which lets an agent recognize the tool without opening the schema. It does not explicitly contrast itself with siblings like flowzap_create_playground or flowzap_export_graph, keeping it 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 Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no named alternative. An agent cannot tell from the description whether this should be preferred over flowzap_create_playground or flowzap_export_graph, nor under what preconditions it should be called.

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.