Skip to main content
Glama

export_laravel_migrations

Read-only

Generate Laravel migration files from a saved diagram or DBML source, with one migration per table and a separate foreign-key migration.

Instructions

Generate Laravel migration files (one per table, plus a foreign-keys migration) 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_laravel_migrations"
  }
}

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.4/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 and the description doesn't need to restate it. The description does add useful behavioral detail about the generated artifact set (per-table files plus a foreign-keys migration), but it says nothing about whether anything is written to disk, how the files are returned, or how the two input modes differ in behavior — a notable gap for a generator.

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?

A single front-loaded sentence with zero filler, and the parenthetical efficiently describes the output structure without padding.

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 two-parameter, read-only export tool with full schema coverage, the description covers the essential purpose, and annotations carry the safety profile. The remaining gap is the return format, which matters more than usual because no output schema exists to explain what the generated files look like.

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%, so both parameters are already documented with their own descriptions, giving a baseline of 3. The description adds no clarification about the either/or relationship between diagram_id and dbml_source or precedence if both are supplied, and "for a diagram" mildly under-represents the DBML-text option.

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 and resource ("Generate Laravel migration files") and adds output-shape detail: one file per table plus a foreign-keys migration. This implicitly separates it from export_laravel_models and export_sql, but it never names an alternative, so the differentiation relies on the reader inferring it.

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 guidance on when to pick migrations over models, SQL, or the diagram exporters, and no noted prerequisites. The schema allows either a saved diagram or raw DBML, yet the description only says "for a diagram," leaving the choice of input mode entirely to the schema.

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