Skip to main content
Glama
adamrpostjr

sqlmate-mcp

by adamrpostjr

add_connection

Add a new database connection to your session by providing a connection URL, a credentials file, or individual parameters like type, host, and database.

Instructions

Configure a database connection for this session. Provide ONE of: (a) url — a connection URL like mysql://user:pass@host:3306/db or sqlite:///path/to/db.sqlite, (b) file — an absolute path to a .sqlmaterc (JSON) or .env file containing DB credentials, (c) individual params — type (mysql|sqlite|mssql), host, port, username, password, database, and optionally name. After adding, call list_connections to verify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoConnection URL (mysql://, sqlite://, sqlserver://)
fileNoAbsolute path to a .sqlmaterc or .env file
hostNoDatabase host
nameNoDisplay name for this connection
pathNoFile path for SQLite databases
portNoDatabase port
typeNoDatabase type
databaseNoDatabase name
passwordNoDatabase password
usernameNoDatabase username
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the configuration action and suggests a verification step, but lacks details on side effects, idempotency, or error handling.

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

Conciseness5/5

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

The description is a single paragraph of four sentences, front-loaded with the purpose, includes examples and a post-usage suggestion, and has no redundant words.

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?

Given 10 parameters with full schema coverage, no required fields, and no output schema, the description adequately covers how to use the tool and what to expect, but lacks details on success/failure behavior or error handling.

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

Parameters4/5

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

Schema coverage is 100% with basic descriptions; the description adds significant value by explaining the three connection modes with concrete URL examples and clarifying optionality among parameter groups.

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 states 'Configure a database connection for this session' with a specific verb and resource, and clearly distinguishes from sibling tools like list_connections and run_query.

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

Usage Guidelines4/5

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

It enumerates three mutually exclusive modes (url, file, individual params) and recommends calling list_connections to verify, providing clear usage context without explicit alternatives or when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adamrpostjr/sqlmate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server