Skip to main content
Glama
wirdes

db-mcp-tool

!pg

Establish and manage PostgreSQL database connections. Input host, database, user, and password to interact with the database securely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionYes

Implementation Reference

  • Inline handler for the !pg tool that initializes a PostgreSQL DatabaseService and connects to the database.
    async (args: { connection: DatabaseConnectionConfig }) => {
      try {
        const config: DatabaseConfig = {
          type: 'postgres',
          connection: args.connection
        };
        dbService = new DatabaseService(config);
        await dbService.connect();
        return {
          content: [{ type: "text", text: "Successfully connected to PostgreSQL database!" }],
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        return {
          content: [{ type: "text", text: `PostgreSQL connection error: ${errorMessage}` }],
          isError: true,
        };
      }
    }
  • src/index.ts:50-72 (registration)
    Registration of the !pg tool on the MCP server with its schema and handler function.
    server.tool(
      "!pg",
      postgresConnectionSchema,
      async (args: { connection: DatabaseConnectionConfig }) => {
        try {
          const config: DatabaseConfig = {
            type: 'postgres',
            connection: args.connection
          };
          dbService = new DatabaseService(config);
          await dbService.connect();
          return {
            content: [{ type: "text", text: "Successfully connected to PostgreSQL database!" }],
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : 'Unknown error';
          return {
            content: [{ type: "text", text: `PostgreSQL connection error: ${errorMessage}` }],
            isError: true,
          };
        }
      }
    );
  • Zod schema defining input parameters for PostgreSQL connection.
    const postgresConnectionSchema = {
      connection: z.object({
        host: z.string(),
        port: z.number().optional(),
        database: z.string(),
        user: z.string(),
        password: z.string(),
      }),
    };
  • DatabaseService.connect() method implementation, specifically the PostgreSQL connection logic (lines 18-22).
    async connect(): Promise<void> {
        switch (this.config.type) {
            case 'postgres': {
                const config = this.config.connection as any;
                this.postgresClient = new pg.Client(config);
                await this.postgresClient.connect();
                break;
            }
            case 'mysql': {
                const config = this.config.connection as any;
                this.mysqlConnection = await mysql.createConnection(config);
                break;
            }
            case 'firestore': {
                const config = this.config.connection as any;
                this.firestoreClient = new Firestore(config);
                break;
            }
        }
    }
  • TypeScript interface for database connection config used by !pg schema.
    export interface DatabaseConnectionConfig {
        // PostgreSQL ve MySQL için
        host?: string;
        port?: number;
        database?: string;
        user?: string;
        password?: string;
        // Firestore için
        projectId?: string;
        keyFilename?: string;
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/wirdes/db-mcp-tool'

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