Skip to main content
Glama
Sign In

AI Flowchart

by io.aiflowchart
OverviewDiscussionsAdmin

Render Mermaid as an image

render_diagram
Read-onlyIdempotent

Turn Mermaid diagram text into a hosted PNG and SVG image URL (cached on a CDN). Use it when a diagram has to go somewhere that cannot run Mermaid: email, Slack or Teams messages, PDFs, Word/Google Docs, Confluence, WhatsApp, a README. Returns the URLs plus ready-made Markdown and HTML. Free — no AI credits.

Input Schema

NameRequiredDescriptionDefault
styleNo"aiflowchart" (default) draws it in AI Flowchart's polished board style; "mermaid" gives the classic Mermaid look. Unsupported diagram types fall back to classic automatically.
themeNoOptional colour theme (default "default").
mermaidYesMermaid source, e.g. "flowchart TD\n A[Start] --> B{OK?}"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / style
      Added value: +{
+  "description": "\"aiflowchart\" (default) draws it in AI Flowchart's polished board style; \"mermaid\" gives the classic Mermaid look. Unsupported diagram types fall back to classic automatically.",
+  "enum": [
+    "aiflowchart",
+    "mermaid"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so safety is covered. The description adds genuinely new behavioral context: output is cached on a CDN, returns URLs plus ready-made Markdown and HTML, and is free with no AI credit consumption. It doesn't discuss failure modes for invalid Mermaid syntax, which is a minor gap.

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 sentences, zero filler. The core capability is front-loaded, followed by the usage condition and return shape. Every clause earns its place.

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

Completeness5/5

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

Although there is no output schema, the description compensates by stating the return values (image URLs plus Markdown and HTML). Combined with annotations covering safety and a fully documented schema, an agent has everything needed to call this correctly.

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 description coverage is 100%, including enum explanations for style and theme, so the schema carries parameter meaning. The description adds nothing about style/theme selection; baseline 3 applies when the schema does the heavy lifting.

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 concrete verb and resource: 'Turn Mermaid diagram text into a hosted PNG and SVG image URL.' The input type (Mermaid source) and output type (hosted images) are unambiguous. It does not explicitly name or contrast with similar siblings like create_diagram or code_to_flowchart, so sibling 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 Guidelines4/5

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

Gives a clear, concrete when-to-use condition: destinations that cannot run Mermaid (email, Slack/Teams, PDFs, Word/Google Docs, Confluence, WhatsApp, README). It stops short of naming an alternative tool or stating when NOT to use it (e.g. when rendering locally or building a diagram interactively), so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AI Flowchart toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources