db-introspector-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | The database connection URL |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesC | Tablas de un schema (default public). |
| describe_tableC | Columnas, tipos y nullability. |
| list_foreign_keysC | Foreign keys del schema. |
| er_dotB | Graphviz DOT a partir de tablas + FKs. Pásalo a diagram-studio render_diagram engine=graphviz. |
| schema_summaryB | Conteo de tablas, FKs y lista compacta. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing tables, describing a table's columns, listing foreign keys, generating an ER diagram in DOT format, and providing a schema summary. There is no overlap or ambiguity between them.
Most tools follow a verb_noun pattern (list_tables, describe_table, list_foreign_keys), while er_dot and schema_summary use noun phrases. The style is still consistent (lowercase with underscores) and the deviations are minor and understandable.
Five tools is a well-scoped count for a database introspector. Each tool covers a specific aspect of schema discovery and diagram generation without unnecessary bloat or missing essentials.
The tool set covers core introspection needs: tables, columns, foreign keys, ER diagram generation, and a summary. Minor gaps like indexes or views are missing, but the current surface is sufficient for typical schema exploration and diagram workflows.