Skip to main content
Glama

maket_mermaid

Render Mermaid diagrams as SVG in page HTML. Supports flowcharts, sequence, class, ER, state, and XY chart diagrams.

Instructions

When to use: add a diagram to a page. Works for flowcharts, sequence, class, ER, state, and XY chart diagrams. Pick this over manual SVG or nested divs when the thing you want is conceptually a graph.

Renders Mermaid syntax to SVG and injects it into the page HTML. The diagram scales with its wrapper (width/height drive the frame, not the SVG itself). If dataId already exists, the diagram is replaced in place — idempotent edits. Header on its own line: graph TD\n A-->B (NOT graph TD; A-->B)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bgNoBackground color (hex). Overrides theme bg.
fgNoText/foreground color (hex). Overrides theme fg.
docYesDocument name
codeYesMermaid diagram syntax. Header on its own line, then statements. E.g. "graph TD\n A-->B\n B-->C".
lineNoLine/connection color (hex). Overrides theme line.
pageYesPage number (1-based)
themeNoBuilt-in theme name. Can be combined with custom color overrides.
widthNoCSS width for the wrapper (e.g. "180mm", "100%"). Default: auto.
accentNoArrow/accent color (hex). Overrides theme accent.
dataIdNodata-id for the wrapper element. Default: auto-generated (mermaid-1, mermaid-2...)
heightNoCSS height for the wrapper (e.g. "120mm"). Default: auto.
positionNoWhere to insert relative to target. Default: beforeend.
targetIdNodata-id of parent element to insert into. Default: page root.
Behavior4/5

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

No annotations provided, so description must disclose full behavior. It explains rendering Mermaid to SVG, injection into HTML, scaling characteristics, and idempotent updates via dataId. Missing error handling or permission details, but overall transparent for a modification tool.

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?

Highly concise: three focused paragraphs with no filler. Front-loads purpose and usage, then adds technical detail and syntax tip. Every sentence adds value.

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?

Given 13 parameters and no output schema or annotations, the description covers overall purpose, usage, key behaviors, and a syntax hint. It does not detail all optional params, but schema compensates. Sufficient for effective tool understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds behavioral context beyond schema for width/height (scaling behavior) and code (syntax hint), enhancing understanding of these parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool adds diagrams to a page, lists supported diagram types (flowcharts, sequence, etc.), and distinguishes from siblings like manual SVG or nested divs by noting it's for conceptually graph-based content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly tells when to use ('when the thing you want is conceptually a graph') and provides alternatives to avoid (manual SVG, nested divs), giving clear guidance on appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ng-galien/maket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server