Skip to main content
Glama
wirdes

db-mcp-tool

!export-data

Export data from specified database tables to external formats using the MCP-enabled server db-mcp-tool, supporting PostgreSQL, MySQL, and Firestore.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYes

Implementation Reference

  • src/index.ts:289-320 (registration)
    Registers the "!export-data" MCP tool. Defines the input schema (table name) and the handler function that delegates to DatabaseService.exportTableData().
    server.tool(
      "!export-data",
      {
        table: z.string(),
      },
      async (args: { table: string }) => {
        if (!dbService) {
          return {
            content: [{ type: "text", text: "You must connect to a database first!" }],
            isError: true,
          };
        }
    
        try {
          const data = await dbService.exportTableData(args.table);
          return {
            content: [
              {
                type: "text",
                text: data,
              },
            ],
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : 'Unknown error';
          return {
            content: [{ type: "text", text: `Failed to export table data: ${errorMessage}` }],
            isError: true,
          };
        }
      }
    );
  • The direct handler function for the "!export-data" tool, which validates the database connection and invokes the service method.
    async (args: { table: string }) => {
      if (!dbService) {
        return {
          content: [{ type: "text", text: "You must connect to a database first!" }],
          isError: true,
        };
      }
    
      try {
        const data = await dbService.exportTableData(args.table);
        return {
          content: [
            {
              type: "text",
              text: data,
            },
          ],
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        return {
          content: [{ type: "text", text: `Failed to export table data: ${errorMessage}` }],
          isError: true,
        };
      }
    }
  • Zod input schema for the tool: requires a 'table' string parameter.
    {
      table: z.string(),
    },
  • Core helper method in DatabaseService that exports table data as SQL INSERT statements for PostgreSQL and MySQL.
    async exportTableData(tableName: string): Promise<string> {
        switch (this.config.type) {
            case 'postgres': {
                if (!this.postgresClient) {
                    throw new Error('PostgreSQL connection not found');
                }
    
                // Önce tablo verilerini al
                const dataQuery = `SELECT * FROM ${tableName};`;
                const result = await this.postgresClient.query(dataQuery);
    
                if (result.rows.length === 0) {
                    return '';
                }
    
                // Sütun isimlerini al
                const columns = Object.keys(result.rows[0]);
    
                // INSERT ifadelerini oluştur
                const insertStatements = result.rows.map(row => {
                    const values = columns.map(col => {
                        const val = row[col];
                        if (val === null) return 'NULL';
                        if (typeof val === 'string') return `'${val.replace(/'/g, "''")}'`;
                        return val;
                    });
                    return `INSERT INTO ${tableName} (${columns.join(', ')}) VALUES (${values.join(', ')});`;
                });
    
                return insertStatements.join('\n');
            }
            case 'mysql': {
                if (!this.mysqlConnection) {
                    throw new Error('MySQL connection not found');
                }
    
                // Önce tablo verilerini al
                const [rows] = await this.mysqlConnection.query(
                    'SELECT * FROM ??',
                    [tableName]
                );
    
                if (rows.length === 0) {
                    return '';
                }
    
                // Sütun isimlerini al
                const columns = Object.keys(rows[0]);
    
                // INSERT ifadelerini oluştur
                const insertStatements = rows.map((row: any) => {
                    const values = columns.map(col => {
                        const val = row[col];
                        if (val === null) return 'NULL';
                        if (typeof val === 'string') return `'${val.replace(/'/g, "''")}'`;
                        return val;
                    });
                    return `INSERT INTO ${tableName} (${columns.join(', ')}) VALUES (${values.join(', ')});`;
                });
    
                return insertStatements.join('\n');
            }
            case 'firestore': {
                throw new Error('SQL data export is not supported for Firestore');
            }
            default:
                throw new Error('Unsupported database type');
        }
    }
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