dlt
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pipelinesB | List all available dlt pipelines. Each pipeline has several tables. |
| list_tablesB | List all available tables in the specified pipeline. |
| get_table_schemaC | Get the schema of the specified table. |
| execute_sql_queryD | – |
| get_load_tableC | Retrieve metadata about data loaded with dlt. |
| get_pipeline_local_stateC | Retrieve the pipeline state information. Includes: incremental dates, resource state, source state |
| get_table_schema_diffC | Get the diff between schema versions of a table. |
| display_schemaB | Generate a mermaid diagram to represent the pipeline schema pipeline_name: name of the pipeline hide_columns: when True, the columns are hidden |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| infer_table_reference | Generates guidelines to infer table references for a given pipeline |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a distinct purpose: display_schema for diagram, execute_sql_query for running SQL, get_load_table for load metadata, get_pipeline_local_state for state, get_table_schema for schema, get_table_schema_diff for version diff, list_pipelines for pipeline listing, list_tables for table listing. No overlap.
All tools follow a consistent verb_noun pattern with snake_case (e.g., display_schema, get_table_schema, list_pipelines). No mixing of conventions.
With 8 tools covering pipeline inspection, schema viewing, state retrieval, and query execution, the count is well-scoped for a data pipeline management server.
The tool set covers inspection and querying comprehensively (list, schema, state, load info, SQL execution), but lacks lifecycle operations like creating or deleting pipelines, which may be intentional for a read-only server.