Skip to main content
Glama

export_mermaid

Read-only

Generate Mermaid erDiagram syntax from a saved diagram or raw DBML source, so you can turn database schemas into diagrams for Mermaid-compatible tools.

Instructions

Generate Mermaid erDiagram syntax for a diagram.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_mermaid"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagram_idNoA saved diagram to export (its UUID).
dbml_sourceNoOr export unsaved DBML text directly instead of a saved diagram.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one behavioral fact beyond that — the output is specifically Mermaid erDiagram syntax, not arbitrary diagram types — but says nothing about how the two optional inputs interact or what is returned when neither is supplied.

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 ten-word sentence with the verb and resource front-loaded and no wasted phrasing. It is lean, though the leanness is part of why guidance is missing rather than a model of efficiency.

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?

For a simple read-only, zero-required-param tool with full schema coverage and no output schema, the description is minimally adequate. It omits that the two parameters are mutually exclusive alternatives and that neither is required, leaving the agent to rely entirely on the schema.

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%, and each property already documents its role, including that dbml_source is an alternative to diagram_id. The description adds no syntax, format, or precedence detail beyond that, so the baseline 3 applies.

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+resource: generate Mermaid erDiagram syntax for a diagram. The 'erDiagram' qualifier usefully narrows the output format and implicitly separates it from siblings like export_plantuml or export_sql, though it does not name an alternative explicitly.

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 description gives no when-to-use guidance, no mention that it can operate either on a saved diagram or on raw DBML, and no exclusion against the other export_* tools. An agent must infer the choice purely from the schema property text.

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