Skip to main content
Glama

import_plantuml

Read-only

Converts PlantUML entity syntax into DBML text for import. Use it to translate PlantUML diagrams, then pass the result to create_diagram or update_diagram to save.

Instructions

Convert PlantUML entity 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": {
      "plantuml": "<plantuml>"
    },
    "name": "import_plantuml"
  }
}

Input Schema

NameRequiredDescriptionDefault
plantumlYesThe PlantUML entity source to convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.4/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, and the description reinforces this with 'never touches the server' while adding the non-obvious fact that the output is transient and must be handed to another tool. It stops short of describing the return shape or error behavior for malformed PlantUML.

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, front-loaded with the core transform and followed by the critical persistence caveat; no filler or redundancy.

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 simple single-parameter transform with no output schema, the description covers purpose, safety profile, and the required next step. Only the exact return value (a DBML string) is left implicit rather than stated.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents it fully. The description adds no format or syntax detail about the PlantUML input beyond what the schema states, so the baseline 3 applies.

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 PlantUML entity syntax into DBML text'), which unambiguously separates it from the sibling import_mermaid and import_sql converters and from the export_* tools.

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 the agent what this tool does not do ('never touches the server') and names the exact follow-up tools (create_diagram or update_diagram) needed to persist the result, so the when-to-use and what-next are both covered.

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