Skip to main content
Glama
Jaskirat-2004

Superset MCP

superset_database_create

Create a new database connection in Superset from a SQLAlchemy URI and required configuration details, using only explicit user-provided credentials.

Instructions

Create a new database connection in Superset

IMPORTANT: Don't call this tool, unless user have given connection details. This function will only create database connections with explicit user consent and input. No default values or assumptions will be made without user confirmation. All connection parameters, including sensitive credentials, must be explicitly provided by the user.

Makes a POST request to /api/v1/database/ to create a new database connection in Superset. The endpoint requires a valid SQLAlchemy URI and database configuration parameters. The engine parameter will be automatically determined from the SQLAlchemy URI prefix if not specified:

  • 'postgresql://' -> engine='postgresql'

  • 'mysql://' -> engine='mysql'

  • 'mssql://' -> engine='mssql'

  • 'oracle://' -> engine='oracle'

  • 'sqlite://' -> engine='sqlite'

The SQLAlchemy URI must follow the format: dialect+driver://username:password@host:port/database If the URI is not provided, the function will prompt for individual connection parameters to construct it.

All required parameters must be provided and validated before creating the connection. The configuration_method parameter should typically be set to 'sqlalchemy_form'.

Args: engine: Database engine (e.g., 'postgresql', 'mysql', etc.) configuration_method: Method used for configuration (typically 'sqlalchemy_form') database_name: Name for the database connection sqlalchemy_uri: SQLAlchemy URI for the connection (e.g., 'postgresql://user:pass@host/db')

Returns: A dictionary with the created database connection information including its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYes
database_nameYes
sqlalchemy_uriYes
configuration_methodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: it's a write operation (POST request), requires sensitive credentials, has automatic engine determination logic, includes URI format requirements, and mentions validation before creation. The only gap is lack of explicit mention of authentication requirements or rate limits, but it covers most critical behavioral aspects for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately front-loaded with purpose and critical warnings, but contains some redundancy (e.g., repeating 'explicit user consent' concepts) and includes implementation details like the specific API endpoint path that don't help tool selection. The Args/Returns sections are helpful but could be integrated more seamlessly. Some sentences could be more efficiently phrased.

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 creation tool with 4 required parameters, 0% schema coverage, no annotations, and no output schema, the description provides substantial context: purpose, prerequisites, behavioral details, parameter semantics, and return value information. It covers authentication implications through credential requirements and includes error handling context (validation before creation). The main gap is lack of explicit error response information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing rich semantic context for all 4 parameters. It explains engine auto-determination from URI prefixes, typical values for configuration_method, the purpose of database_name, and detailed format requirements for sqlalchemy_uri including examples. The description adds significant value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'Create a new database connection in Superset' with a specific verb ('create') and resource ('database connection'), distinguishing it from sibling tools like superset_database_list, superset_database_update, and superset_database_delete. It explicitly differentiates this creation function from other database-related operations.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance with 'IMPORTANT: Don't call this tool, unless user have given connection details' and specifies prerequisites ('explicit user consent and input', 'All connection parameters... must be explicitly provided by the user'). It clearly states when NOT to use the tool (without user confirmation) and what conditions must be met before invocation.

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

Deploy Server

Other Tools