Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SCHEMASKETCH_EMAILNoEmail address for SchemaSketch login when not using a token.
SCHEMASKETCH_TOKENNoSchemaSketch token generated from the web app. Can be read-only or read & edit.
SCHEMASKETCH_PASSWORDNoPassword for SchemaSketch login when not using a token.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_dbml_syntax_guideA

Read this before writing or editing any DBML — the exact syntax SchemaSketch accepts, with a full example.

list_diagramsA

List the signed-in user's saved diagrams (id, name, last updated).

get_diagramA

Fetch one diagram by id, including its full DBML source and table positions.

validate_dbmlA

Parse DBML and report syntax errors plus semantic warnings (duplicate names, dangling refs, unrecognized/mismatched types) before saving it. Read-only — never touches the server.

create_diagramA

Create a new diagram. The DBML is validated first: syntax errors or relationships to missing tables/columns mean nothing is saved; warnings are returned with the result.

update_diagramA

Replace a diagram's DBML source (and/or rename it). This overwrites the whole source — fetch it with get_diagram first if you need to edit rather than replace it outright, and pass its version as base_version so you never overwrite someone else's newer change. New DBML is validated first: errors mean nothing is saved; warnings are returned with the result.

delete_diagramA

Permanently delete a diagram. This cannot be undone — confirm with the user before calling it.

export_sqlB

Generate CREATE TABLE / ALTER TABLE SQL DDL for a diagram, in a given dialect.

export_laravel_migrationsB

Generate Laravel migration files (one per table, plus a foreign-keys migration) for a diagram.

export_laravel_modelsB

Generate Laravel Eloquent model files (fillable, casts, and inferred relationships including belongsToMany through plain pivot tables) for a diagram.

export_mermaidB

Generate Mermaid erDiagram syntax for a diagram.

export_plantumlC

Generate PlantUML entity syntax for a diagram.

import_sqlA

Convert CREATE TABLE / ALTER TABLE SQL DDL into DBML text. Read-only — never touches the server; pass the result to create_diagram or update_diagram to actually save it.

import_mermaidA

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.

import_plantumlA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 15 tools

Disambiguation5/5

Each tool has a clearly distinct resource+action: CRUD on diagrams (list/get/create/update/delete), read-only converters (import_sql/import_mermaid/import_plantuml), generators (export_* per format), plus validate_dbml and get_dbml_syntax_guide. The import/export prefixes make directionality explicit, so import_plantuml vs export_plantuml cannot be confused. The descriptions actively reinforce the read-only vs persisted-write boundary.

Naming Consistency5/5

Uniform snake_case verb_noun pattern throughout: list/get/create/update/delete_diagram, import_*/export_*, validate_dbml. The only mild irregularity is get_dbml_syntax_guide being longer, but it still follows verb_noun and reads clearly.

Tool Count5/5

Fifteen tools for a diagram editor with multi-format import/export is well-scoped: 5 CRUD, 3 imports, 5 exports, plus validation and a syntax guide. Each tool maps to a distinct format or lifecycle operation rather than duplicating another.

Completeness4/5

Core lifecycle is fully covered: list/get/create/update/delete, validation, syntax help, three import formats and five export formats. Minor gaps exist such as no duplicate/rename-only helper (rename is folded into update_diagram) and no per-table or partial-edit operation, forcing whole-source replacement, but these are workable.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues