Skip to main content
Glama

Generate Database from DDL

generate_database
Destructive

Executes normalized DDL against a supplied JDBC URL to create the schema and tables, refusing existing-table collisions unless confirm=true.

Instructions

Execute proposed normalized DDL against a user-supplied JDBC URL to create the schema (creates only; refuses existing-table collision unless confirm=true).

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": {
      "jdbc_url": "<jdbc_url>",
      "ddl": "<ddl>"
    },
    "name": "generate_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
ddlYesProposed DDL to execute (one or more statements), alternative to path
urlNoAlias for jdbc_url
pathNoFile inside an allowed root containing DDL (alternative to ddl)
confirmNoExplicit consent to create tables when a target table already exists (default false)
jdbc_urlYesJDBC URL of the target database (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: it is create-only and will abort on existing-table collisions unless confirm=true. That collision guard and consent rule are not in the annotations and materially change how an agent should call it. It still doesn't say what happens on failure or whether statements run transactionally.

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?

One sentence with no wasted words, front-loading the action and target while the collision/confirm condition is parenthetically attached where it is immediately relevant.

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 destructive schema-mutation tool with no output schema, the description covers the key risk (table collision and the confirm escape hatch) and the create-only scope. Missing pieces are secondary: failure behavior, transactionality, and what 'normalized' implies about the expected DDL.

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 coverage is 100%, so the schema already documents jdbc_url, ddl, path, url alias, and confirm. The description reinforces the confirm consent semantics but adds no new syntax or format detail beyond that baseline.

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 resource: execute DDL via a JDBC URL to create a schema. 'Creates only' implicitly distinguishes it from a destructive migration tool and from export_schema_ddl, which runs the reverse direction, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

It states the operating condition (only creates; refuses on collision unless confirm=true), which tells the agent when to pass confirm. It does not say when to use this versus query_database or how it should follow analyze_schema_normalization, so usage context is implied rather than spelled out.

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