mcp-sqlalchemy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_URL | Yes | SQLAlchemy URL for database connection (e.g., virtuoso+pyodbc://user:password@VOS) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| podbc_get_schemasC | Retrieve and return a list of all schema names from the connected database. |
| podbc_get_tablesC | Retrieve and return a list containing information about tables in specified schema, if empty uses connection default |
| podbc_describe_tableC | Retrieve and return a dictionary containing the definition of a table, including column names, data types, nullable, autoincrement, primary key, and foreign keys. |
| podbc_filter_table_namesC | Retrieve and return a list containing information about tables whose names contain the substring 'q' in the format [{'schema': 'schema_name', 'table': 'table_name'}, {'schema': 'schema_name', 'table': 'table_name'}]. |
| podbc_execute_queryC | Execute a SQL query and return results in JSONL format. |
| podbc_execute_query_mdB | Execute a SQL query and return results in Markdown table format. |
| podbc_query_databaseC | Execute a SQL query and return results in JSONL format. |
| podbc_spasql_queryC | Execute a SPASQL query and return results. |
| podbc_sparql_queryC | Execute a SPARQL query and return results. |
| podbc_virtuoso_support_aiD | Tool to use the Virtuoso AI support function |
| podbc_sparql_funcD | Call ???. |
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 11 tools
Multiple tools have overlapping or unclear purposes, causing confusion. For example, podbc_execute_query and podbc_query_database both execute SQL queries and return results in JSONL format, making them nearly indistinguishable. Additionally, podbc_sparql_func and podbc_virtuoso_support_ai have vague descriptions that don't clearly differentiate their functions from other query tools.
The naming follows a consistent prefix pattern (podbc_) and uses snake_case throughout, which is predictable. However, there are minor deviations like podbc_spasql_query (likely a typo for SPARQL) and inconsistent verb usage (e.g., get_schemas vs. filter_table_names), but overall the structure is readable and mostly uniform.
With 11 tools, the count is reasonable for a database interaction server, covering schema exploration, table queries, and specialized functions. It's slightly on the higher side but still manageable, as each tool appears to serve a distinct technical purpose, though some redundancy exists.
The toolset covers core database operations like querying, schema retrieval, and table description, but there are notable gaps. For instance, there are no tools for data manipulation (e.g., insert, update, delete) or transaction management, which are essential for a complete SQLAlchemy-like interface. The inclusion of SPARQL and specialized functions adds niche coverage but doesn't fill these basic CRUD gaps.