Skip to main content
Glama

import_mermaid

Read-only

Convert Mermaid erDiagram syntax into DBML text for use with diagram creation or update tools; this read-only step never modifies server data.

Instructions

Convert Mermaid erDiagram syntax into DBML text. Read-only — never touches the server; pass the result to create_diagram or update_diagram to actually save it.

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": {
      "mermaid": "<mermaid>"
    },
    "name": "import_mermaid"
  }
}

Input Schema

NameRequiredDescriptionDefault
mermaidYesThe Mermaid erDiagram source to convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'never touches the server' is largely redundant. However, the description adds genuine workflow behavior beyond the annotations: the output is DBML text that must be fed into create_diagram or update_diagram, which tells the agent this is a pure transformation step. Error behavior on malformed Mermaid input is not covered.

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 short sentences with no filler. The core action is front-loaded and the workflow caveat follows immediately, so nothing needs to be skimmed for.

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?

For a single-parameter, read-only converter this covers the essentials: what it consumes, what it emits, and that it does not persist. Without an output schema, a brief note on failure behavior for invalid Mermaid would have made it fully complete.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already fully documents it; per the calibration baseline this scores 3. The description's phrase 'erDiagram syntax' reinforces the dialect restriction but does not add constraints or examples beyond the schema text.

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?

States a specific verb and resource ('Convert Mermaid erDiagram syntax into DBML text') including the exact source dialect and target format. This cleanly separates it from import_plantuml, import_sql, and the export_* siblings without any schema inspection.

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?

Explicitly tells the agent that this tool does not persist anything and that the result must be passed to create_diagram or update_diagram to save it — a concrete next-step routing rule. The choice against import_plantuml/import_sql is implied by input format rather than stated, so it falls short of full when/when-not guidance.

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