Skip to main content
Glama

export_plantuml

Read-only

Convert a saved diagram or raw DBML text into PlantUML entity syntax for database schema visualization.

Instructions

Generate PlantUML entity 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_plantuml"
  }
}

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say the result is returned as text rather than written to a file (despite the word 'export'), nor anything about output format or size limits.

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. It is efficient, though its brevity is close to under-specification rather than disciplined conciseness.

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 two-parameter read-only generator with no output schema, the description is minimally adequate but silent on the return value and on the mutually exclusive choice between the two inputs. An agent can call it thanks to the schema, not the description.

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 the schema itself explains that dbml_source is the alternative to a saved diagram_id. The description adds no meaning beyond that, so the baseline of 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?

The description gives a specific verb and output artifact ('Generate PlantUML entity syntax'), so an agent knows the transformation being performed. It does not contrast itself with the sibling exporters (export_mermaid, export_sql, export_laravel_*), which would be needed for 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 mention that either a saved diagram or raw DBML may be supplied, and no statement about when to pick this over the other export_* tools. Only the tool name implies the export context.

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